Folks,
After a hub rebuild, we now see that jobs created from deployments and executed (all via API) are immediately discarded and removed on successful completion.
How can we prevent this?
Thanks
Mick
It seems that it’s a default setting now in the latest version of HUB 1.17.0 to delete completed successful jobs. The API deployed jobs are unaffected. Its when you use the UI for a deployment.
Wonder if there was a global override
Hi. As per the documentation:
For newly created schedules, service deployments, and trigger deployments, the default behavior is now to delete jobs immediately after successful execution, helping free up executor resources. Failed jobs are still retained for debugging. Existing deployments are unaffected.
Have you tried checking the Advanced settings of a Data App? Or the requirement is to globally change it back for all Data Apps by default?
1 Like