Recover Unsaved Integration Changes
You can recover unsaved changes in an integration that crashes during design time because of a browser crash, loss of network connectivity, a server going down, and so on.
As you design an integration, a backup copy is created whenever you complete a task such as configuring an action, deleting an invoke connection, configuring business identifier tracking, or defining global faults. There is no time limit in which you need to log back in and recover your changes. The unsaved changes remain as long as the integration is not unlocked by an administrator.
The following data in an integration cannot be recovered after a crash:
- Changes made while editing an action (for example, you are designing a stage file action when your integration crashes)
- Changes made while working inside the mapper
- Layout changes such as repositioning an action
- Connections page edits
- Any changes in a basic routing integration
Recovery behavior is different based on the roles assigned to the user. For example, assume you are designing the following integration when your browser crashes.
- Design an integration as a user with the
ServiceDeveloper role. Assume you have not yet saved
your changes for the following integration when your browser
crashes.
- If you log back in as that same user with the
ServiceDeveloper role, note the following behavior
for recovering your unsaved changes.
- If you instead log in as a user with the
ServiceAdministrator role, note the following
behavior.