Setting a trigger to wake a paused digital process
Digital processes that have already started, may need to wait for an intermediate event before continuing with its next steps. While waiting, a digital process enters a dormant state.
Instance ID as a wake up trigger
To wake up a sleeping process instance, you need to post an event with a ce-cxpinstanceid (Instance ID) header and the ce-type header that matches the event type that had been configured for the process as a trigger.
ce-cxpinstanceid routes to the correct instance
ce-type routes to the trigger
The Instance ID is the ID of a running instance of a digital process. Every time a trigger event is received for an Orchestration Engine digital process, Orchestration Engine generates a new instance with an Instance ID. If the digital process is triggered 100 times, Orchestration Engine creates 100 unique Instances, each with their own ID.
To find the Instance ID header in Make, go to your scenario and check the completion summary of the process that was already run. In the Orchestration window you can check the Instance ID and copy the value.
Enter the copied value for the ce-cxpinstanceid header in your request.If you send the request with the ce-cxpinstanceid and ce-type headers, Orchestration Engine saves the payload and then passes it through to the next Make scenarios that are configured as next steps in your Orchestration Engine digital process. The event type is used as a key. The payload grows with every event that is generated.
Notification module in Make as a wake up trigger
It is also possible to wake up a digital process with a Make scenario that ends with a "completion event" module that is configured to send notifications about a completed scenario to Orchestration Engine. If such a Make scenario is a part of your digital process steps, it causes the digital process to wake up and move to the next process steps.
To learn more about Make modules, see the Make Modules documentation.