Stop and Start a Process Automation Instance
You can stop and start any standalone Oracle Cloud Infrastructure Process Automation instances. To stop or start a child Process Automation instance, you have to perform the action on the parent Oracle Integration instance. After a stop request is initiated, the Process Automation instance goes into the inactive state. During the inactive state, no new processes are started. Inactive service instances are paused. When the processes are no longer running, the Process Automation instance goes into a completely inactive state. During this state, the workspace and designer capabilities are unavailable.
Oracle recommends the following:
- Do not stop Process Automation instances running in a production environment.
- Start or stop a Process
Automation instance in either of two ways:
- Select the action to perform:
-
To stop your Process Automation instance, select Stop, then select Stop again when prompted to confirm your selection.
The instance state changes to Updating during the pausing process. When complete, the state changes to Inactive in the State column.
This action causes the following to occur:
- For execution pack and active user SKU based instances, the billing stops for the duration that the instance is paused.
- Database purging continues to run.
- REST APIs are unavailable for use. If you attempt to use the APIs while your Process Automation instance is in a paused state, you receive an error message.
-
To resume your Process Automation instance, select Start, then select Start again when prompted to confirm your selection.
Note
You cannot start an Process Automationinstance when maintenance and security patching are in progress.The Process Automation instance state changes to Updating during the resumption. When complete, the state changes to Active in the State column.
-