# Recent calls and failing-call alerts

> See every recent call your Chirp's Actions made and how it went, and what happens when calls keep failing.

Source: https://www.chirpbuilder.com/help/actions/recent-calls  
Plans: Essentials, Creator, Business, Academy  
Last checked: 2026-10-27

When you're done, you can tell whether your Chirp's Actions are working.

**Who can see this:** everyone who can open the Chirp in the editor, viewers included.

## Recent calls

Near the bottom of **7. Actions**, open **Recent calls**. It appears once there's been a call or a
confirmation.

![Recent calls opened: two changes visitors were asked to confirm (one confirmed and sent, one cancelled), then calls with when, the operation, from Visitor or Your preview, the result (Worked, or API error with HTTP 401) and the time each took.](https://mjmtbasmrtksluvlnema.supabase.co/storage/v1/object/public/help-media/web-optimized/actions/recent-calls/SS-ACT-060-01__recent-calls__essentials__detail__v01.webp?v=2761623910)

- **Changes visitors were asked to confirm:** when, which operation, from a **Visitor** or **Your
  preview**, and the answer: **Waiting**, **Confirmed** (while it's sent), **Confirmed, sent**,
  **Confirmed, failed**, **Cancelled** or **Expired**, with the HTTP status, like "Confirmed, sent
  (200)". The newest 30 show.
- **Calls:** when, the operation, where from (**Visitor**, **Your preview** or **Test**), the result
  and how long it took.

The results:

| Result | Meaning |
|---|---|
| Worked | The API answered fine. |
| API error (…), like API error (401) | The API said no: 401 or 403 usually means the key, 404 the address or values. |
| Blocked | Not allowed: an address that isn't public, or a redirect to another address. |
| Timed out | No answer within 20 seconds. |
| Couldn't connect | The address couldn't be reached, or it redirected too many times. |
| Bad values | What the AI wanted to send didn't match the schema. |

"Only the operation and the result are kept (calls for 30 days, confirmations for 90). No questions,
answers, sent values or keys." Older entries are cleared out as new calls come in, so a quiet Chirp can
still show older ones. The list shows the newest 50 calls.

## When calls keep failing

- **In the editor:** when half or more of an Action's calls in the last 24 hours failed (at least 3),
  its card says "Calls are failing: … of … in the last 24 hours", with a note on what to check. Your
  preview's calls count too; tests don't. API errors, Blocked, Timed out and Couldn't connect count as
  failed; Bad values don't.

  ![The Plant shop Action with Calls are failing: 4 of 4 in the last 24 hours outlined, and a red note that the API refused the sign-in for recent calls.](https://mjmtbasmrtksluvlnema.supabase.co/storage/v1/object/public/help-media/web-optimized/actions/recent-calls/SS-ACT-060-02__failing-warning__essentials__desktop__v01.webp?v=7175b55eb4)

- **By email:** when the last 5 calls of an Action all failed, the account owner gets an email, "Your
  Chirp "…": the Action "…" keeps failing", at most once a day for each Action.

While you fix it, you can turn Actions off: see
[Turn Actions off, replace a schema, or remove an Action](https://www.chirpbuilder.com/help/actions/turn-off-replace-remove). Then test an operation: see
[Test an Action](https://www.chirpbuilder.com/help/actions/test).