Skip to Content
Puppi
Concepts

Staleness

See when a model or destination will run again.

Staleness decides whether a model or a destination has work to do. It is computed when an attempt is about to run. A source is not gated this way: it runs whenever the run or its schedule reaches it, and the engine decides afterwards whether the result is new.

Read the verdict

puppi assets --env prod

Environment flags are in the CLI reference.

ReasonMeaning
never_materializedThe asset has no latest materialization.
input_newerAn upstream latest is newer than the one this asset consumed.
input_unconsumedAn upstream has a latest, and this asset consumed none of it.
definition_changedThe asset’s code_version on the latest materialization differs from the active deployment.

A model or a destination whose verdict is current is skipped. The attempt stamps verified_at on the current latest and writes no new materialization. puppi run --force runs every planned asset anyway.

See Materializations for how a source decides that nothing new arrived.

After a code change

Deploying new code writes no materialization by itself. The asset becomes stale because its code_version changed, and the next run rebuilds it. A one-line change in one asset’s run changes that asset’s version. Assets whose source did not change stay current.

A rollback moves latest to an older materialization. That older row is not newer, so staleness does not carry the rollback downstream. Rollback walks those assets and repoints or rebuilds them.

Schedule an asset

schedule: { every: "15m" }
schedule: { cron: "0 * * * *", timezone: "UTC" }

every is a clock-aligned cadence, not a delay from now: 15m fires at minute 0, 15, 30, and 45; 2h at every even hour; 1d at midnight. 23h expands to 0 */23 * * * and fires at 00:00 and 23:00, not 23 hours after the last run. cron is five fields: minute, hour, day of month, month, day of week. A bad expression fails at puppi build. The engine checks timezone when it accepts the deployment.

The engine fires a due asset once a minute. A scheduler that was down fires once when it returns. It does not replay the missed window.

Pause schedules

puppi env pause --env prod
puppi env resume --env prod

env pause and env resume take the same environment flags as puppi assets. See Choose an environment.

Pause stops schedules in that environment. puppi run still starts a manual run.