Managing and monitoring
Edit, pause, resume, and delete Automations, read what each run delivered, and understand why Nalar pauses one.
Once an Automation is running, its detail panel is where you check what it did and change what it does next. Only you, as its creator, can open it.
The detail panel
Select an Automation in your list to open its details.
It shows the name, status, kind of Automation, schedule or condition with its timezone, next run, Agent, channels, who it is delivered to, and the message.
Edit, pause, resume, delete
The actions available depend on the Automation's status.
| Status | Actions |
|---|---|
| Active | Edit, Pause, Delete |
| Paused | Edit, Resume, Delete |
| Finished | Delete |
Edit opens the same form you used to create it. Nothing changes until you select Save changes, and every field is checked again before saving. You can't switch a scheduled Automation into a Signal or the other way round; create a new one instead.
Pause stops future runs and keeps the settings and run history.
Resume checks the whole configuration again, then turns future runs back on. Runs that were due while it was paused aren't made up.
Delete asks you to confirm, stops all future runs, and removes the Automation from your list.
Run history
Run history lists every attempt in order, with its time and whether it was a test or a normal run. Each run has one of four outcomes:
| Outcome | What it means |
|---|---|
| Success | The Agent finished and every configured channel delivered. |
| Partially delivered | At least one channel delivered and another didn't, for example Email but not WhatsApp. |
| Blocked | A check stopped the run before anything was delivered, such as access or an unavailable channel. |
| Failed | The run started but the Agent or the delivery failed. |
Success always means the message was delivered, not only that the Agent produced an answer. Blocked and Failed runs show a reason you can act on.
Expand a run to read what the Agent produced, and switch to see how it looks as an Email or a WhatsApp message. Opening a run never sends anything again or starts a new run. The preview shows the saved result in today's format; it isn't a receipt of the exact message you received.
The run count on an Automation counts normal runs only, not tests.
When Nalar pauses an Automation
Nalar can pause an Automation by itself, for example when it can no longer run safely with your access. It doesn't send a separate notification, so check your list if an Automation goes quiet.
| Likely cause | What to do |
|---|---|
| You lost access to its Agent or data | Contact your Department Head or Nalar Support. Once access is back, review and resume it yourself. |
| The Agent you chose was removed | Contact your Workspace Owner, Workspace Admin, or Nalar Support. Edit the Automation to pick another Agent you can use, then resume it. |
Nalar doesn't resume a paused Automation automatically when access comes back. Before you resume one, open it and check which Agent it will use.
Missed and late runs
If a run was due while Nalar was unavailable, it runs once when service comes back, even if late. Several missed runs of the same Automation become one late run, and the schedule then continues as normal. Paused Automations don't catch up.
One-time Automations
After a One-time Automation runs, it moves to the Finished group and won't run again. Check its run history to confirm the message was delivered.