Hello @Preeti zade ,

Most of these requirements can be achieved by creating a reference table. For example, you can create a table called API_Logs that contains fields such as API name, last run date, IsSuccess, and other relevant details.

You can then use this table as a reference for all the chained APIs and build your logic around it, whether for retry mechanisms, tracking execution status, or logging purposes.

Hi Preeti,

Adding a few best-practice points:

1. Failure tracking

• Use Exception Handlers in Service Actions to capture the exact failure point.
• Log details using ExceptionMessage() and ExceptionStack().
• Maintain a correlation ID to track the full API chain.

2. Retry mechanism

• OutSystems doesn’t support automatic retry → needs custom logic.
• Retry only for transient errors (timeouts, network).
• Limit retries (1–2 max).
• Store last successful step to resume from failure point.
• Prefer Timer-based retry instead of immediate retry.

3. Email notification

• Avoid sending emails directly in flow.
• Log first, then use a Timer to send aggregated failure emails.

4. Good practices

• Keep APIs idempotent for safe retry.
• Avoid tight coupling between APIs.
• Don’t log sensitive data.

Thanks and Regards,
Akshay Deshpande