Tasks can now be configured to expire automatically in the queue

Developers can set Time-To-Live (TTL) limits for background tasks globally or per-task, ensuring stale jobs expire before executing if queues back up.
Background tasks sometimes sit in queues longer than they are relevant. Developers can now set a Time-To-Live (TTL) for tasks to ensure they expire instead of running too late.
This limit is configurable globally in the project config, on specific tasks, or overridden at the moment of execution. This prevents stale operations—like sending a time-sensitive notification—from firing after their window has passed. The change touches the core SDK and the run engine, resolving limits dynamically without slowing down the primary task trigger pipeline.
1export default defineConfig({2 project: "my-project",3 ttl: "1h", // Applies to all tasks by default4});
View Original GitHub Description
Add TTL (time-to-live) defaults at task-level and config-level, with precedence: per-trigger > task > config > dev default (10m).
Docs PR: #3200 (merge after packages are released)