Read Each Layer Separately
| Layer | What to inspect | Meaning |
|---|
| Connection | Timeout, network error, unreadable response | The client cannot yet establish the operation result. |
| HTTP | Actual response status | Transport/request handling; does not replace the API result. |
| API | Result.Code and Result.Message when present | Application-level processing result; interpret according to the returned contract. |
| Signals | Returned values and the configured model | Decision/model output, when supplied. |
| Business outcome | Disposition code and observed transaction/session state | What happened in the interaction, not an HTTP or API error code. |
Handling Failures
- Inspect the actual response before assuming an input, authorization, or service problem.
- For authorization failures, verify the key scope and ActionKey type without exposing credentials in diagnostics.
- For field errors, use the ActionType guide and field definitions.
- For connection failures or timeouts, establish whether the event was received before retrying.
- Preserve correlation identifiers and sanitize logs before sharing them with IH.
Use the provisioned integration contract for numeric result meanings and retry policy. Confirm whether a timed-out event was received before treating a retry as a new operation.