Review automation runs

Each time a rule matches an event, Kluvan keeps a run with its source, its outcome and the record it created. Runs that need approval wait here, and failed runs can be tried again.

Before you start

• You need the right View Automations to read runs, and Manage Automations to approve, reject or retry them.

Steps

1. Open Workflows → Automations and select the Run history tab.
2. Read each run's status: Completed, Awaiting approval, Failed or Rejected.
3. Select a run to open it. The details show the source app, record type and event, and the error for a failed run.
4. For a run Awaiting approval, open Approve and select it to create the record, or open Reject, type the reason in Details and select Reject.
5. For a Failed run, fix the cause first, for example give the rule's owner back the right they lost or switch the target app on. Then open Retry and select it.
6. On a completed run, select Open linked record to go to the ticket or work order it created.

Good to know

• Approving or retrying a run checks the rule again: it must still be active, and its owner must still have the rights it needs.
• A run creates its record once. Approving or retrying twice does not create two records.
• You can also reject a failed run you do not want to retry.
• You are not alerted when an automation run fails (workflow rules do alert their owner). Look at Run history regularly, especially after changing rights or switching apps off.
• Retrying a failed run has been checked less than the other steps. After a retry, open the linked record to confirm it was created.
• Analytics can count automation runs by status alongside other apps. See Build an analytics dashboard.
• To change what a rule does, see Create an automation. Runs of workflow rules have their own history.