Skip to main content
Executions lists every run, newest first, including public form requests. Search by the reference shown after you submit, filter by status or client, and click Refresh for new runs.

Follow a run: finding it by its reference, its steps and their output, and reading a failed step (1:14).

The Executions page with a Search executions box, All statuses and All clients filters, and a table of runs such as Core · Password Reset · Acme Corp (Completed), Core · Onboarding · Initech (Running) and Core · Password Reset · Globex (Failed), with execution IDs and created dates.

Open a run

1

Click a row

A failed run opens on Why it failed: the cause, who fixes it, the steps and what to do once it’s fixed. What happened lists what the run did, and Steps lists every step. A running run shows what it’s waiting for.
An open run, Core · Onboarding · Acme Corp, Failed. Why it failed: The new user's domain isn't verified in Microsoft 365, Failed at Create User, This needs you with two numbered steps, Once it's fixed: Retry the run, a Retry the run button, Ask the assistant and Details. What happened: Ticket created, User not created.
2

Click a step

Its output opens alongside. A failed step’s output holds the error on one line: scroll along it to read it all.
The Reset Password step detail with an error status and an Output block whose error begins internal: failed to reset Microsoft user password.
To approve or reject a waiting run, use Approvals.

Fix a failed run

1

Fix the cause

Follow the steps under Why it failed, or click the button that opens the setting, such as Open the onboarding settings.
2

Retry the run

Click Retry the run, then Retry.
A retry starts from the top with the same answers and the workflow’s current settings, and keeps the original PSA ticket. If the run had an approval, the confirm says the approver is asked again. Admins and the person who submitted the run can retry it. Once a run has created the user or group, Retry isn’t offered and the steps say to finish the rest by hand. To ask about a run, click Ask the assistant.

Create a missing ticket

A run whose PSA ticket wasn’t created still completes, with a warning that says why. Fix the cause, then click Create the ticket now and Create ticket. The confirm says to check your PSA first: the ticket may exist even though Triggr couldn’t confirm it. Only admins see the button.

Runs that need attention

When a run fails or gets stuck, admins see N runs need attention on Home. Click it to list those runs on Executions. A run that fails or gets stuck while you’re in Core also raises a toast, or a card in the assistant if it’s open: click See why to open the run. Opening a run clears it from the count.

Common reasons a run fails

An open run shows these steps for the causes MSPs see most. For Microsoft access problems, see Fix Microsoft connection problems.
  1. Open the workflow’s Ticketing settings and pick a ticket type.
  2. Save, then create the ticket again.
  1. Open PSA setup and choose your PSA as the default.
  2. Create the ticket again.
  1. Open PSA setup → client mapping and map this client to its company.
  2. Create the ticket again.
  1. Check the client has a free seat of the licence (Microsoft 365 admin centre → Billing → Licences).
  2. Check the user has a usage location.
  1. Check the domain in the onboarding settings (Identity) is one of the client’s verified domains.
  2. If it should be, verify it in the client’s Microsoft 365 admin centre (Settings → Domains) and retry; if not, change the setting and submit the request again.

Troubleshooting

Open the run: its warning says why. Fix it, then create the ticket.
The client isn’t linked. Check its Microsoft tenant ID on Clients, click Link to GDAP, then run the workflow again. See No tenant ID.
Open it to see what it’s waiting for, such as the approver on Approvals. A run with nothing happening for over an hour shows Needs a look and what to do.
Next: Approvals.