LogoLogo
CommunitySupport PortalYouTubeStart a free trial
OE (Celonis)
  • Welcome
  • Commerce Engine
  • Orchestration Engine
  • API Documentation
  • Release Notes
  • Changelog
OE (Celonis)
  • Orchestration Engine
  • Getting Started
    • What is OE?
      • What are the benefits?
      • Use Cases
    • Provisioning
    • Understanding Make
    • OE Learning Trails
      • Setting up a First Digital Process
      • Adding a Conditional Step in a Digital Process
  • Management Dashboard
    • Accessing OE
    • Orchestration Center
    • Forms
    • KPIs and Analytics
    • Rulestore
    • Events
      • Event Registry
      • Event Log
      • Cloud Events in OE (Celonis)
      • Events Authentication and Configuration
      • Working with Event Data (Celonis)
    • Admin
      • Users and Roles
      • Integration with Celonis
      • Make Team
      • Task Inbox and Tasks
  • Digital Processes
    • Digital Processes Dashboard
    • Digital Processes Example
    • Working with Digital Processes
      • Digital Process Components
      • Creating a Digital Process
      • Editing a Digital Process
      • Testing a Digital Process
      • Conditional Process Runs
      • OE Make Modules
      • Configuring a Connection between OE and Make Modules
      • Setting a Trigger to Wake Up a Paused Digital Process (Celonis)
      • Cloning of Make Scenarios in OE Digital Processes
    • Data Flow between OE and Celonis
      • Retrieving Data from Celonis
      • Sending Data from OE to Celonis (Celonis)
      • Sending Form Submission Data from OE to Celonis (Celonis)
      • Sending Forms Magic Links Data from OE to Celonis (Celonis)
    • Process Context
    • Datastore
    • Versioning
    • Data Retention Policy
  • Troubleshooting
    • Firewall Allowlisting
    • Digital Processes Debugger
    • Generating a HAR File with Logs
    • FAQ
      • Receiving Alerts for Scenario Errors
      • Make Scenario Not Valid in OE
      • Digital Processes Blocked by Scenario Errors
      • Invalid Digital Processes
Powered by GitBook
LogoLogo

Resources

  • Emporix.com
  • Developer Policy
  • Terms of Use

Find us

  • LinkedIn

© 2025 Emporix. All Rights Reserved.

On this page
  • Make scenario settings
  • Allow storing of incomplete processes
  • Set up a number of consecutive errors

Was this helpful?

Export as PDF
  1. Troubleshooting
  2. FAQ

Digital Processes Blocked by Scenario Errors

See how to proceed when a digital process is blocked with Make scenario errors.

PreviousMake Scenario Not Valid in OENextInvalid Digital Processes

Last updated 9 days ago

Was this helpful?

Make scenario settings

Make's scenario settings provide different options for handling errors and scenarios data storage.

Allow storing 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 scenario step, 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.

To learn more about error handling in Make, see and Make's documentation.

Receiving Alerts for Scenario Errors
Errors