How to preserve job run history when deploying with DABs
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2025 04:14 AM
Hi
I’m having an issue when deploying jobs with DABs. Each time I deploy changes, the existing job gets overwritten, the job name stays the same, but a new job ID is created. This causes the history of past runs to be lost.
Ideally, I’d like to update an existing job while keeping both the job name and the full run history. Has anyone found a best practice or configuration for handling this? Otherwise, I dont see the point of using DABs if history is lost for each?
Thanks in advance!