# Execution limits

A completed action, a business outcome, policy routing and webhook receipt are
separate facts. A CHECK can complete successfully and report missing data. Read
the exit condition and matched policy rule before treating it as a technical failure.

## External effects and uncertain results

An HTTP destination may accept a mutation before execution evidence is committed.
A process crash or timeout in that gap leaves an uncertain result. The engine's
recovery evidence and outbound idempotency keys help reconcile work, but the
destination must honor those keys or expose an audit record. Do not assume
distributed exactly-once delivery or repeat work merely because a screen is stale.

Definitions are shared across lanes; changing a draft or publishing a new version
is separate from changing an entity's binding or pinned policy context. Inspect
the offered concrete sequence and its blocked reason. Missing test connections
do not fall back to production.

## Events and receiving applications

Webhook delivery can retry independently of execution. Receivers must deduplicate
events and reconcile uncertain updates. Retained evidence bounds duplicate
suppression; it is not an unlimited retention promise. Use the [integration guide](https://docs.amonsul.io/developers/integration/)
for signature and receipt handling and [common problems](https://docs.amonsul.io/guides/common-problems/)
for evidence to collect before contacting support.