For the complete documentation index, see llms.txt. This page is also available as Markdown.
Trigger to Wake Up a Paused Process
Configure an action event that resumes a paused value stream.
The value stream that have already started, may need to wait for an intermediate event before continuing with next steps. While waiting, a value stream goes into a dormant (sleeping) state.
Instance ID as a wake up trigger
To wake up a sleeping process instance, you need to post an event with a ce-instanceid (Instance ID) header and the ce-type header that matches the event type that had been configured for the process as a trigger.
ce-instanceid routes to the correct instance
ce-type routes to the trigger
The Instance ID is the ID of a running instance of a value stream. Every time a trigger event is received for a value stream, VSM generates a new instance with an Instance ID. If the value stream is triggered 100 times, VSM 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 has already run. You can check the Instance ID and copy the value.
Enter the copied value for the ce-instanceid header in your request.
If you send the request with the ce-instanceid and ce-type headers, VSM saves the payload and then passes it through to the next Make scenarios that are configured as next steps in your VSM value stream. 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 value stream with a Make scenario that ends with a "completion event" module that is configured to send notifications about completed scenario to VSM. If such a Make scenario is a part of your value stream steps, it causes the process to wake up and move to the next process steps.
