Investigate automation runs and blocked webhooks

Use Run History to inspect executions. For webhook triggers, Blocked Requests shows requests that did not start run.

Example: Diagnose webhook request that did not run

Scenario: Sender reports HTTP 202, but Automation Run History has no entry.

1. Open Run History and check request time.

2. Open Blocked Requests, review Received, From, and Reason.

3. For Wrong or missing token validate sender token; for IP address isn't on the allowed list check source IP and allowlist.

4. Retry after correction, then verify actual run and downstream result. HTTP 202 alone is not success proof.

Review run

1. Open Admin > AI Studio > Orchestrate > Automations and select automation.

2. Select Run History.

3. Review Total runs, Success rate, and Avg duration.

4. Find run by trigger and start time. Check duration, tokens, and status.

5. Open run record for available execution detail.

Review blocked requests

1. Open webhook-triggered automation.

2. Select Blocked Requests.

3. Review Received, From, and Reason.

4. Select Refresh to reload recent list.

Blocked Requests displays latest 20 requests from past 7 days. Examples: IP address isn't on the allowed list and Wrong or missing token.

Webhook callers receive HTTP 202 even when authentication fails. Do not treat 202 alone as proof that automation ran. Check Run History and Blocked Requests.

If over request limit, caller receives HTTP 429.