You can roll back a job migration to restore the data from before the migration.
Rollback is useful if a migrated job malfunctions.
After you roll back a legacy pipeline-based job:
- The migrated custom job all prior executions are removed.
- The custom job isn’t accessible.
- Changes to the customer job aren’t saved.
- All executions of the custom job are removed.
- The deprecated job is restored to the deprecated framework.
- The rollback process is logged and is accessible from global jobs log file.
- Migrated string is removed from the deprecated job ID.
- Job executions for the legacy job are accessible from the Job History (Deprecated)
screen.
- Subsequent uses of the job on the deprecated framework are accessible from the Job History
(Deprecated) Screen.
- The legacy job and its data is visible to all users.
- The legacy job date can be changed, exported, and imported.