Goal
Run a new job version safely while your scheduled task keeps using the current, stable version.
Prerequisites
- You have a scheduled task already running on version A.
- You’ve deployed job version B that you want to test.
- Role: Admin (to edit tasks and versions).
Steps
- Pin the current scheduled task to its version
- Go to Task › Task setup of your scheduled task.
- Select the desired Job version = A.
- Uncheck “Follow the new version”.
This pins the task to version A even if new versions are deployed.
- Create a separate test task for the new version
- From the Job or Tasks list, create a new task (e.g.,
MyTask_test). - In Task setup, choose Job version = B.
- Leave the test task unscheduled (manual runs only), or schedule it off-hours for testing.
- Run and validate
- Launch the test task manually.
- Check logs, status, and metrics as usual.
- Promote the new version to production
- When satisfied, go back to the scheduled task:
- Either re-check “Follow the new version” (so it will pick up version B now and future versions),
- or explicitly select Job version = B to stay pinned to B.
- Clean up
- Delete the temporary test task if no longer needed.
Notes & Tips
- Why this works: unchecking “Follow the new version” freezes a task on a specific job version, so your schedule remains stable while you test elsewhere.
- Use a clear naming convention for test tasks (e.g.,
*_test) and keep them manual to avoid accidental runs. - If contexts differ between versions, review Task setup › Context before testing.
- Rollback is instant: just switch the scheduled task back to version A (or keep it pinned).
