{"version":"2.1.267","anchor":"new-deadline-parameter-for-artifact-republishes-hot-mode","canonical_anchor":"new-deadline-parameter-for-artifact-republishes-hot-mode","heading":"New \"deadline\" parameter for artifact republishes (hot mode)","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-deadline-parameter-for-artifact-republishes-hot-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New \"deadline\" parameter for artifact republishes (hot mode)\n\nArtifact republishes can now set a \"deadline\" to force older running copies to stop\n\n**What**\n\nWhen republishing an artifact (an update to something already published, sometimes called \"hot\" mode), the artifact tool's prompt now documents an optional `deadline` field. It accepts values like `\"now\"`, `\"15m\"`, `\"1h\"`, `\"24h\"`, `\"7d\"`, or a specific ISO timestamp, and forces older running copies of the artifact to stop by that time. This is gated behind a schema flag (`hotOn`), and the field only applies to republishes, not ordinary edits, where it should be omitted.\n\n**Why**\n\nThis gives control over how long an outdated running copy of a republished artifact is allowed to keep running before it's shut down, rather than leaving that unbounded.\n\n- Area: Artifacts\n- Names: `deadline`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}