Orchestration Engine troubleshooting FAQ
You can configure your Make organization to receive different kinds of notifications related to your scenarios: warnings, errors or deactivations. You can either receive the notifications by email or check them inside the Make application under Notifications.
Email notification options
To set up your Make email preferences:
Log in to your organization in Make.
Go to My Team > Team > Notification Options.
Choose the notification that you want to receive by email.
Why do I receive emails about failed processes but not about incomplete ones?
There's no distinction between a failed process and incomplete process when it comes to notifications sent from Make. This is because an incomplete process run is a failed process scenario with errors or warnings. What is different between the two is that a scenario is not shut down immediately. The state is saved when the process fails.
We recommend you to enable all the notifications in Make, to be sure not to miss any issues.
If everything is correct but you still don't receive the emails, check your spam folder or contact your administrator to check if the messages are not blocked on your side.
Orchestration Engine does not send any error notifications itself. However, you can check the Digital Process Debugger for existing issues.
If a scenario that you prepared in Make is not visible in the list of scenarios available for your digital process in Orchestration Engine, check if you have the following settings:
Start trigger must end with a Start New Orchestration module. Check Events as Triggers.
Mid trigger must have a notification event - Completion Event module. Check Setting a Trigger to Wake Up a Paused Digital Process.
Scenario in a process step must start with Trigger Event and have the Completion Event module.
Orchestration Engine doesn't currently support scenarios without the Completion Event module. If you don't have the module for the scenarios used as mid triggers or process steps, Orchestration Engine filters them out and they are not available for you to use.
Make's scenario settings provide different options for handling errors and scenarios data storage.
Allow storage of incomplete processes
The storage of incomplete processes is not enabled by default. To enable it go to Your scenario > Scenario Settings.
If the storage of incomplete processes is not enabled, the scenario stops and all instances of process contexts are blocked. With this setup, the overall outcome is that you have a queue of process context instances, which are blocked at a specific step in a scenario, until the scenario is manually reactivated.
If the storage is enabled, you can check the records of the incomplete processes at any time in the Incomplete Processes folder. You can use the record to reprocess the data. The incomplete processes need to be resolved to unblock the specific process context instance.
Set up a number of consecutive errors
The consecutive errors feature helps to separate sporadic issues from those that are fundamentally broken. Using advanced scenario settings, you can customize the number of failed processes before a scenario gets deactivated.
If the validation shows that a new process is invalid, check for:
proper configuration and reference to Make scenarios.
JSON syntax errors.
Errors in referencing a Make scenario
It's possible that you have a reference to a Make scenario that was either deleted or modified.
Reference to a deleted Make scenario
Check if your digital process references a scenario that had been deleted. If it does, you should see a red error with a Scenario deleted notification message at the location (process step) where the scenario was used.
To resolve this error, remove the reference to the deleted scenario from your process step.
Reference to a modified Make scenario
If a Make scenario has been modified, it may no longer meet the requirements of its intended context. In this situation, the Orchestration Engine UI doesn't show it in the list scenarios available for your digital process. You're not able to use the scenario in your process steps.
This occurs when:
the scenario no longer sends output event information through the Start New Orchestration module.
the scenario no longer sends output event information through the Completion Event module.
the scenario no longer receives incoming calls through the Trigger Event Make module.
To resolve the errors, make sure the modified Make scenario meets the requirements of the intended context and check if all the input and output modules are configured properly, with correct events setup.
JSON syntax
As the digital processes are designed using the Orchestration Engine UI, you are unlikely to see any syntactic errors. However, if your digital process doesn't work, and you've checked all the Orchestration Engine and Make settings but the errors still occur, you may need to review the JSON document to ensure it adheres to proper structure and formatting.