Skip to main content

Celonis Product Documentation

Action Flows terms and limitations

Here's an explanation of some of the terminology used across Action Flows.

  • Execution log storage (30 days)

    Execution log storage refers to the number of days that you can access detailed logs for every execution. These logs are stored for 30 days. For more information on logs see monitor your Action Flow.

  • Maximum file size (2 GB)

    The maximum file size that can be automated and processed. The maximum size of a single file is limited to 214,7483,648 bytes. Some modules can accept a file in their input and/or yield a file in their output. If the maximum file size is exceeded, Celonis proceeds in accordance with the settings of the enable data loss option. For more information, see Working with files.

  • Maximum Action Flow execution time (40 min)

    The maximum time for which a single Action Flow can run. Maximum Action Flow execution time should not exceed 40 minutes. If execution time is exceeded, the Action Flow will fail with a timeout error. For more information, see Action Flow execution, cycles, and phases


    Ongoing module executions are not interrupted immediately. The actual execution time until timeout might be a bit higher.

  • Minimum interval between scheduled Action Flows (1 min)

    The minimum interval is the shortest possible time in-between two successive scheduled Action Flow runs. The minimal interval is 1 minute. You can set the interval in the schedule settings.


    Note: This is not effective when scheduling is set to immediately (instant triggers).

  • Webhook queue size (10k executions)

    All incoming webhooks are stored in a Webhook queue. The queue can start filling up when the Action Flow responsible for processing the webhooks is disabled (e.g. due to an error) or is processing the webhooks at a slower rate than they are being received. The maximum size of a single input/output webhook queue is 10,000 executions. For more information, see Webhooks.