Help: Inbox

Read a request

Each request an agent submits appears as a card. You see the same card in the Inbox, in History and at the top of the request's own page.

Everything on a card except the status, the times and the policy explanation is what the agent submitted. funwatcher does not check that the summary, the counterparty, the amount or the payload are true, and it does not carry out the action.

The card

Part of the cardWhat it means
Agent name (top left)The agent that submitted the request, by the name you registered it under.
Action type (top right, in capitals)The kind of action the agent proposes: payment, message, delete, post, sign, account change or other.
Status (next to the action type)Where the request stands now, such as pending or held. See Request statuses.
Summary (the large line)The agent's one-sentence description of what it wants to do. In a list it is a link to the request's own page.
CounterpartyWho or what the action is directed at, as named by the agent. The row is absent when the agent gave none.
AmountThe currency code followed by the amount. The row is absent when the request carries no amount.
Reversible"yes" or "no": whether the agent says the action can be undone afterwards.
ExpiresShown on a pending request. A live countdown, then the exact time in UTC in brackets. If nobody decides before this time, the request expires.
ReleasesShown on a held request in place of Expires. A live countdown, then the exact time in UTC. At this time the hold ends and the agent may proceed. See Held actions.
SubmittedWhen the request arrived, in UTC.
Policy explanation (the sentence under the fields)Why your rules gave this outcome.
ButtonsShown only when the request is pending or held and you are allowed to decide it. See Approve, deny or edit a request and Roles.

The countdown

The countdown updates every second and reads like "in 4m 9s". It adds hours and days when the time left is longer. When the time has passed it reads "now". The card leaves the Inbox when the request expires or is released.

The policy explanation

The explanation names the rule that decided the outcome, its priority, its outcome and the kinds of condition that matched, for example:

Rule "Payments require approval" (priority, require_approval) matched on action_type_in.

The rule's priority number appears where the example says "priority".

The explanation is written once, when the request arrives. Changing your rules later does not change it. See How rules work.

The request's own page

  1. In the Inbox or in History, select the summary of a card.
  2. Read the sections below the card.
SectionWhat it shows
DetailsRequest id, Account, Policy outcome, Expires, Hold until (held requests only) and Decided (once someone approved or denied it).
PayloadThe exact parameters the agent says it will act with, as JSON.
DecisionsEach decision with who made it and when, the note if one was given, and the edited payload if it was changed.
Execution reportsWhat the agent reported afterwards: executed or failed, with its reference and detail if it gave them.

An execution report is the agent's own statement. funwatcher records it and cannot confirm that the agent did what it reported.

Next:

All help pages

Inbox

Rules

Teams

Ledger

Billing

Account and security

For agent builders

Troubleshooting