A Worker Bee’s flight history is the record of every time it has run and what happened. Check it after creating a bee, and whenever someone asks “did that email go out?”

Before you start

You need workerbees:read:automations or workerbees:admin:automations. Without either, Worker Bees shows “You don’t have access to Worker Bees”.

Open the flight history

  1. Go to Worker Bees → All Worker Bees. The list shows each bee’s Name, Description, Status and Last Run (Never if it hasn’t run).
  2. Select a bee’s row, or focus it and press Enter. Its Flight History opens.
  3. Use the page controls at the bottom to see earlier flights.

Choose Worker Bees at the top to go back to the list.

Read each flight

There’s one row for each action each time the bee runs, so a bee with two actions records two rows per event.

Column What it shows
Status Succeeded or Failed, with a reason under some failures
Triggered by The event’s technical name, for example ContactCreated
Action type The action’s key, for example relationships.email-contact (see Actions and their settings)
Started When the action started
Duration How long it took

Flights are kept for 90 days.

What Failed means

Failed means the action didn’t complete and won’t be tried again. A reason appears under the status for problems with the bee itself:

Reason shown What to do
The automation owner no longer has active access to this beehive. The bee’s owner, usually the person who created or last saved it, no longer has access. Someone with access needs to save the bee again through the Worker Bees API, which makes them its owner
The automation owner no longer has permission to run this action. The owner has lost a permission the action needs. Restore it, or have someone who holds it save the bee again through the API
An authorized user must save this automation before it can run. The bee has no owner, usually because it was created before bees had owners. Someone with access needs to save it again through the API
This automation is inactive or has been deleted. The bee was switched off or removed after the event happened

For other failures, such as a contact who hasn’t consented or a webhook that answered with an error, the row shows Failed without a reason. The full detail is recorded on the flight and your administrator can read it through the Worker Bees API. The how-to for each action lists its common causes:

Retried flights

When a failure looks temporary, such as the receiving service being briefly unavailable or not answering in time, ThirdSectorBee tries the action again automatically. It doesn’t retry problems that won’t fix themselves, such as missing consent or a wrong setting, so you’ll see those as Failed straight away.

While a flight is waiting to be retried, its row may show no status and no meaningful duration. Reload the page later. If it never settles, give your administrator the bee’s name and the Started time. There’s no button to replay a flight yourself.

If no flight appears

  • Check the bee is Active in the list.
  • Check the event really happened, and on a record the bee’s owner can see.
  • Check the bee’s filters. Several filter types never match today; see Which filters work today.
  • In a swarm, check that a branch matched. If none did and there’s no fallback, nothing runs and nothing is recorded.

Last Run shows when the bee last finished an action, not that every action succeeded. Use the flight history to be sure.