Troubleshooting Runs
When an automation does not do what someone expected, Qlar always leaves a reason — on the automation itself (its status reason) and on each run (its outcome and error code). This page explains every one and what to do about it.
You see them in the Monitor (Automations → Monitor → select a row) and users see the same reasons, in friendlier words, on their Automations page.
First questions
| Symptom | Look at |
|---|---|
| "It didn't run." | The automation's status. Only Active automations run. Then the Next run time, and whether the policy switch is on. |
| "It ran but I got nothing." | The run's Condition — Condition not met is normal. Then the Actions column for a failed or skipped action. |
| "It ran late." | Runs can start a minute or more after their time, and later when many are due at once. Consider scheduling a few minutes earlier. |
| "It stopped by itself." | The status reason — see the first table below. |
| "The agent won't offer to create one." | The user must be signed in, outside the CMS preview, and the policy must be on with Create automations allowed. |
Why an automation is in its status
| Reason (Monitor) | Status | What it means | What to do |
|---|---|---|---|
| Paused by its creator | Paused | The user paused it. | Nothing. They can resume it. |
| Paused by a contributor | Paused | Someone on your team paused it in the Monitor. | Resume it from the Monitor when ready. |
| Disabled by a contributor | Turned off | Someone on your team disabled it. The user cannot resume or edit it. | Resume it from the Monitor, or the user can delete it. |
| Paused: more active automations than the policy allows | Paused | You lowered Maximum Active Automations. The newest above the limit were paused. | Raise the limit, or ask the user to delete some. |
| Paused: the agent moved to another organization | Paused | The agent was transferred. | Users resume what they still want, after checking it. |
| Stopped after repeated failures | Stopped | Three runs failed in a row. | Check the history for the cause (below), fix it, then resume. |
| Stopped: runs more often than the policy allows | Stopped | You raised Minimum Interval above its schedule. | The user edits the schedule, then resumes. |
| Stopped: its trigger is no longer allowed | Stopped | The trigger kind was removed from Allowed Triggers. | Allow it again, or the user recreates it. |
| Stopped: none of its actions is allowed any more | Stopped | All its actions were removed from Allowed Actions. | Allow an action again, or the user edits it. |
| Stopped: its creator lost access to the agent | Stopped | The user left the organization or lost access to the agent. | Restore the access, or delete the automation. |
| Stopped: its content could not be read | Stopped | The encrypted content is unavailable (Privacy Mode). | Ask the user to recreate it. |
| Its schedule has finished | Finished | A one-time run happened, or the end date passed. | Nothing. Removed after 7 days. |
| Reached the policy's limit of runs | Finished | Maximum Runs per Automation was reached. | Raise the limit, or the user creates a new one. |
Once you have fixed the cause, use Resume in the Monitor (if you may manage automations) or ask the user to resume from their page. Resuming checks the policy again, so it will refuse if the cause is still there.
Why a run failed or was skipped
Each run in the history shows one of these codes.
Policy and limits
| Code | Meaning | What to do |
|---|---|---|
| Automations are switched off in the policy | The master switch is off. The run is skipped, not lost. | Switch it back on. |
| Trigger not allowed by the policy / No action allowed by the policy | Your policy no longer allows it. | Adjust the policy. |
| Runs more often than the policy allows | The interval is below the Minimum Interval. | The user edits the schedule. |
| User's daily run quota reached | Maximum Runs per User per Day is used up. | Raise it, or ask the user to reduce how often theirs run. |
| Run limit reached | Maximum Runs per Automation reached. | Raise the limit. |
Credit and budget
| Code | Meaning | What to do |
|---|---|---|
| Organization credit exhausted | There is not enough credit to run. | Buy credits or set up auto top-up. |
| Member budget or agent limit reached | The user's budget for this agent, or the agent's own limit, is used up. | Raise the budget or the agent limit. |
The run itself
| Code | Meaning | What to do |
|---|---|---|
| Timed out | The run took longer than Run Timeout. | Raise the timeout, or simplify the task or condition. |
| The agent's run failed | The agent could not finish. Temporary failures are retried automatically. | Check the Monitoring Logs. If your tools are down, repair them. |
| A selected skill is no longer available | A skill the automation used was removed. The run continues without it. | Restore the skill, or the user edits the automation. |
| Content could not be read | The encrypted content is unavailable. | Ask the user to recreate it. |
| Agent not found | The agent was deleted or unpublished. | Restore or republish it. |
| Creator no longer has access | The user lost access to the agent. | Restore access. |
Timing
| Code | Meaning | What to do |
|---|---|---|
| Skipped: started too late | The automation uses Skip as its missed-run policy and could not start on time. | Change its missed-run policy, or wait for the next run. |
| Superseded by a newer schedule | The user edited it and a newer run replaced this one. | Nothing — this is expected. |
| Abandoned | The run was interrupted before it finished. | Nothing, unless it repeats. |
| Paused platform-wide | Qlar paused all automations for a moment. | Nothing. Runs resume. |
| Code | Meaning | What to do |
|---|---|---|
| Invalid WhatsApp number | The number cannot be a real phone number. | The user corrects it. |
| Daily WhatsApp limit reached | Maximum WhatsApp Messages per Day is used up. | Raise the limit. |
| WhatsApp rate limit reached | Too many messages went to this number in an hour. Qlar tries again later. | Nothing. |
| No WhatsApp sender available | The platform's WhatsApp number is offline. | Try again later; contact support if it persists. |
| WhatsApp rejected the message | WhatsApp refused it. | Check that the number can receive WhatsApp messages. |
| WhatsApp send failed | The message could not be sent. | Nothing at first; it is retried. |
| WhatsApp outcome unknown | Qlar cannot tell whether it arrived. It is not retried, to avoid a duplicate. | Ask the user whether it arrived. |
Retries
A temporary failure — for example an AI provider that is busy — is retried up to Maximum Retries times, waiting Retry Interval minutes between attempts. Each attempt is a separate line in the history, marked Retry. A WhatsApp message is never sent twice, and a run that never got as far as sending it is safe to retry.
Three runs in a row that fail after all retries stop the automation (Stopped after repeated failures). A single success resets the count.
Still stuck?
Ask the user for the automation's name and the time it should have run, find it in the Monitor, and read its history. If the history shows nothing at all at that time, check that the automation was active and that the policy was on. For anything in this page that you cannot resolve, contact Qlar support with the automation's name and the run time.