Execution & Logs

Flows follow a strict and predictable lifecycle:

1. A trigger event occurs
2. Matching flows are identified
3. Flow executions are scheduled
4. Conditions are evaluated at runtime
5. Actions are executed asynchronously
6. Results are logged

Flows execute in parallel. If multiple flows are scheduled for the same time, they all run at the same time.

---

Retries And Failures

If an action fails (for example due to an external service issue):

• It is retried up to three times
• If it still fails, it is marked as failed
• The failure is visible in the flow log

Failures do not:

• Stop other actions
• Stop other flows
• Affect the underlying booking/payment/consent form

---

Cancelling A Scheduled Flow

Scheduled flow executions can be cancelled.

To cancel:

1. Open the booking/payment/consent form
2. Remove the selected flow from the flows section

Once removed, any future scheduled executions of that flow will not run.

---

Flow Logs

Bookings (and other flow targets) include detailed flow logs. The log shows:

• Which flows ran
• Which actions executed
• Success or failure status
• What data was processed
• Retry attempts

Flow executions are immutable. Logs always reflect exactly what happened at execution time.