Skip to main content

Why Didn't My Agent Send Its Report?

Why a Weflow agent's report did not arrive, how to read its run History, and how to fix an agent that did not run, found nothing or failed.

When an agent's report does not arrive, the agent did not run, ran and found nothing to send, or ran and failed. The agent's History on the AI Agents page tells you which: it lists every run with its start date, duration, status, type, consumed actions and result.

Only Weflow admins can build, edit and manage agents, so an admin runs the checks below.

Causes when an agent doesn't send its report

Cause

How to check

Fix

Agent not active

Status toggle off on AI Agents page

Turn on Active

Schedule not reached yet

Last run column, schedule and timezone

Wait, or change the schedule

Nothing new to send

History shows the run skipped

Widen the lookup or untick Skip

Agent actions ran out

Usage summary shows the plan used

Wait for the 1st or Get More Actions

Run failed or timed out

Failure email, or History status and reason

Narrow the lookup or grant field access

Slack or Teams app not connected

Setup & Integrations in the Admin Console

Connect the Slack or Teams app

Person not a recipient

End step To, Cc and Bcc

Add the Weflow user or team

Check that the agent is active and its schedule has come

A test run does not switch an agent on. After a test passes, the panel reads that the agent isn't active yet: turn on Active in the flow editor, or the Status toggle on the AI Agents page, to run it on schedule.

Then check the schedule. An agent runs Daily, Weekly on the days you selected, or Monthly, at the time and in the timezone you set, and the schedule is its only trigger. The Last run column on the AI Agents page shows when it last ran.

Check whether the agent ran and found nothing to send

With Skip if there are no new results ticked on the End step, nothing is sent when the lookup finds no records, or when the agent returns no text and no report. The agent still runs on its schedule, and its History marks those runs as skipped, no new content.

If the agent should have found records, check the Get/Lookup Record step's conditions: a narrow condition, such as one stage or a short date range, can match nothing in a quiet week. Loosen the conditions, or untick Skip if there are no new results if your team wants the email every time.

Check whether the agent actions ran out

When your workspace has used its agent actions for the month, Weflow stops its agents until actions are available again, without billing overage.

The Usage summary on the AI Agents page shows the actions used against your plan and the reset date. The agents restart on the 1st of the month, or as soon as you move to a larger tier with Get More Actions on the Agent Usage page.

Check whether the agent run failed or timed out

When a scheduled run fails, Weflow emails the admin a failure notice. Open the agent's View History: each run shows its status and, for a failed run, the reason.

  • Too much data: a run can time out when its lookup returns more data than it can process, such as thousands of records or many call transcripts at once. A tighter filter, such as a shorter date range or fewer stages, keeps the run within its limits

  • A field Weflow cannot read: a lookup that filters on a field Weflow's integration user cannot access fails with a Salesforce query error. Grant the integration user access to the object or field in Salesforce

  • A temporary Salesforce error: a run can fail on a passing Salesforce error and succeed on its next run

Check whether the Slack or Teams app is connected

An agent delivers to Slack through the Weflow Slack App and to Microsoft Teams through the Weflow Teams app. Both need the app connected for your workspace in Admin Console > Setup & Integrations.

Without a connected app, the End step offers email only, so a report meant for a Slack or Teams channel never reaches it. Connect the Slack or Teams app, then check the End step's delivery settings.

Check who receives the agent's report

The End step emails Weflow users and teams chosen in To, Cc and Bcc; it cannot send to an outside email address. Once the Slack or Teams app is connected, it can also send the report to Slack or Microsoft Teams.

A team receives the report as its membership changes, so a person added to the team gets the next one, and view-only users can receive reports too.

A test run sends the real result to the agent's own recipients with TEST RUN in the subject. If a test reached your team but the scheduled run did not, check that the agent is Active.

Frequently asked questions about agent reports

Why did my team get an email marked TEST RUN?

Someone ran a test of the agent. A test run emails the agent's recipients, with TEST RUN in the subject, so they see exactly what the agent will send.

Can an agent send its report to an email address outside Weflow?

No. Email recipients are Weflow users and teams only. Once your workspace's Slack or Teams app is connected, an agent can also send its report to Slack or Microsoft Teams.

How do I know an agent ran if it sent nothing?

Open its History. A run that found nothing new, with Skip if there are no new results ticked, is listed as skipped, no new content.

Did this answer your question?