Runs, monitoring and fixing problems
See every run step by step, get told when something breaks, and run it again once it’s fixed.
Runs
Every time an automation runs, Rellova records each step: what it did, when, and what it reported. Open the automation’s Runs tab (or the form’s) to see them.
| Status | Means |
|---|---|
| Queued | About to start. |
| Running | Steps are running now. |
| Waiting | Waiting for an approval. |
| Succeeded | Every step finished. |
| Failed | A step failed. The run says which and why. |
| Needs attention | Rellova stopped rather than risk sending something twice. Check, then decide whether to send again. |
| Rejected | An approver said no, or nobody decided in time. |
Monitoring
Monitoring shows runs across the whole workspace, with filters, so you can spot problems early. Owners and admins are emailed when an automation breaks; you can turn this off under WorkspaceTeam & Access.
Fixing a failed run
- Open the run and read the failed step’s message.
- Fix the cause: reconnect an account on the Integrations page, correct a setting and publish, or fix the data in the other system.
- Retry the run. It carries on from where it stopped, and steps that already sent something aren’t repeated.
Common problems
| Message | What to do |
|---|---|
| Choose a connection on the Integrations page | Connect the service, then choose it in the step. |
| {{…}} isn’t a field on this form | The value’s field was renamed or removed. Pick it again from the list of values. |
| No email address was given in the form | Make the email field required, or add a fallback recipient. |
| Too many emails went to this address | To prevent abuse, Rellova limits how many emails one address gets in an hour. That email was skipped; the rest of the run carried on. |