Editing, disabling, and deleting jobs
Change a job, pause it without losing its definition, or remove it entirely — and understand what each action affects.
Last updated July 17, 2026
#Editing a job
Open a job to change any part of it — source, destination, mode, pattern, schedule, or reliability settings. After a significant change, validate with Run now and review the run before relying on the next scheduled execution.
#Disabling and enabling
Disable a job to stop it running on schedule while keeping its definition intact — useful for maintenance windows or seasonal workflows. A disabled job never runs automatically and shows no next-run time. Re-enable it to resume.
#Deleting a job
Deleting a job removes its definition. Its past run history remains within your retention window for the record. Deleting a job does not delete files at the source or destination, and it doesn't remove the credentials it used.
#Jobs and credentials
Jobs reference credentials by name. Deleting a credential that a job still uses will break that job at its next run — reassign or disable dependent jobs first. See Credential best practices.