We don't have a place to report bugs now? puppet --noop runs consume resource schedules. In Puppet 8 (resource_harness.rb), perform_changes() writes ':checked' to state.yaml even in noop mode, and scheduled?() decides from ':checked'. So a noop run inside a schedule's range counts as that period's evaluation, and the next real run skips the resource. ':synced' is already guarded with '!resource.noop?'; ':checked' should be too. A noop run should not update state.