3803622 - Delay in Scheduled AutoFlow Trigger Execution

• Scheduled Autoflows configured on SLA due dates do not start exactly at the scheduled time.
• Observed delay between the scheduled time and actual start is typically 5–15 minutes.
• No error messages are displayed.

SAP Sales Cloud V2

SAP Service Cloud V2

1. Configure an Autoflow with a scheduled rule based on the SLA completion due date (for example, 3 minutes after case creation).
2. Create a case and wait until the scheduled time elapses.
3. Observe that the Autoflow starts several minutes after the scheduled time (often 5–15 minutes).

Autoflow processing is Asynchronous; execution is queued and depends on system load. Scheduling “on” does not imply an immediate start.

1. Acknowledge that a 5–15 minute delay for scheduled Autoflow execution is expected due to asynchronous processing and system load.
2. Build time-sensitive workflows with resilience to scheduling delays, recognizing that execution may not occur immediately at the configured time
3. Monitor the average execution delay of scheduled rules in the tenant.
4. If the delay consistently reaches about 25 minutes or more, contact support to investigate a potential performance issue.

scheduled autoflow, execution delay, asynchronous processing, schedule rule, SLA due date, completionDueOn, background queue, performance delay, expected behavior, workflow timing, 25 minutes threshold, start delay, run delay, schedule latency, automation timing , KBA , CEC-CRM-AFL , Autoflow for SAP Sales/Service Cloud , Problem