Early access. These guides cover the current product build. Access and connected-channel availability depend on your organization's setup. Public Instagram messaging access is not available yet.
Read the night log
The night log is the record of what your Runners attempted. Each entry names the Runner and shows an action's recorded status. An entry in the log does not always mean a message was sent.
Find an action
Open Night log. Use the Runner, status, and time filters to narrow the list. Expand an entry when you need more detail about the action.
Channel setup entries describe connection steps and have their own label. They are separate from Runner actions. Home's per-Runner totals cover the full preceding 24 hours and exclude channel setup, even when the recent-action feed shows only part of that period.
Channel maintenance entries describe background access checks where enabled. They also stay out of Runner totals. A completed check does not renew access or prove every channel capability. See Connect a channel for connection and reconnect steps.
Where reconnect alerts are available and an owner has opted in, Channel reconnect email entries record a notice attempt separately from Watch briefings and Runner activity. An accepted status means the email provider accepted the notice; it does not confirm delivery or reconnect the channel. Rejected or unknown outcomes are not automatically resent. Check Channels for the current connection status.
What the status means
- Done: The action completed. Read the action type too: a contact update is different from a message send.
- Failed: The action did not complete as expected. Read its details before taking another action.
- Held by a guardrail: A rule stopped the action, such as a limit or a closed messaging window.
- Test mode: Test mode prevented the external action.
- Needs you: The action needs a decision. It has not been sent.
- In progress: The action has been recorded, but a final outcome has not been recorded yet.
When a failed attempt was held before contacting the provider
Some Failed entries explain that the last attempt was held before contacting the provider. Read that explanation alongside the status:
- Other requests were still in progress.
- Requests were temporarily paused.
- The request check was unavailable.
These explanations describe the last recorded attempt, not every earlier step in the Play. The entry still appears as Failed in its badge, filters and Runner counts. It does not become Held by a guardrail.
This does not promise a scheduled retry or eventual delivery. It also does not restore an allowance or refund usage already recorded for the action. Check the latest log entry before deciding what to do next; do not assume the whole Play was unsent just because one attempt was held.
These request checks are off by default and available only where enabled for connected Facebook and Instagram Runner activity: Echo replies, Keep profile lookups and Post catalog reads. They do not cover reconnecting a channel, background token checks or AI calls. Workspace access and provider approval still determine which capabilities are available.
When something needs you
Check Home for confirmation cards. Read the Runner, recipient, and proposed text before choosing Approve or Skip. An expired card cannot authorize an action.
If a channel needs attention, check its connection before expecting new activity. A quiet log can also mean there were no matching events or the Runner was switched off.
Keep previews separate
Testing a Play does not add entries to the night log. Use a sample to understand a rule; use the log to inspect recorded activity.