Activity lists a published workflow’s runs from the last 30 days, newest first. To see it, open a workflow and select Activity at the top.
Check what a workflow did
Each run shows the survey of the response it ran for, who answered when Usertick knows, its status and when it started. A threshold alert’s run shows Threshold alert. Each run has one of these statuses:
- Queued means the run is waiting for its turn, or for a Wait to end.
- Sending means a step is running.
- Retrying means a step failed for a temporary reason, and Usertick tries it again later.
- Sent means the run reached the end of the flow.
- Failed means a step failed and the run stopped there.
- Skipped means the run sent nothing, and the run shows the reason, such as “The workflow was turned off.”
- Held means the run arrived while failures paused the workflow, and it waits until the workflow is turned on.
Select a run to open it. The run shows its status, the respondent and when it started, then each step with its tool and status. A failed or skipped step says why, and Show the provider’s message shows the tool’s own error message. Under the steps, Response shows the data the run started from, and Sent and Received show what the selected step sent and what the tool answered. Open response opens the response in the Inbox, and the back arrow returns to the list.
When a step fails
- Temporary problems. When a tool doesn’t answer, Usertick tries the step again several times over about six hours, and the run shows Retrying.
- A failed run. A step that still fails, or that the tool refuses, ends the run, and the steps after it don’t run. After you fix the cause, open the run and select Retry to send it again from the failed step. When you changed the step’s settings and published the workflow, Retry uses the published settings. If the published workflow no longer has that step, Retry uses the settings the run started with.
- A skipped step. Usertick skips a step with nothing to send, such as an event step for a response without a user ID, shows the reason and continues the run. A skip doesn’t count as a failure.
After 20 failed runs in a row, Usertick pauses the workflow and notifies members whose role has Manage workflows. While the workflow is paused, Usertick holds the responses that would have started it, up to 1,000 and for up to 7 days. After you fix the step, select Turn on, and the held runs proceed in the order they arrived.
When a tool refuses its connection, members whose role has Manage integrations receive a notification, such as “Slack is failing”, at most once a day per connection.
When the survey changes
Publishing a survey pauses a workflow on it when the new version removes or changes something the workflow reads:
- a question the workflow reads is removed or changes type,
- an option a condition checks for is removed,
- the scale of a question that a condition or an alert compares on changes,
- a variant a condition names is removed.
Before such a publish, the survey editor lists the affected workflows under Publishing pauses a workflow, and afterward, A workflow was paused offers Open workflows. Turn on doesn’t restart a workflow paused this way, so edit it, fix what it reads and select Publish workflow.
Dropping a language from the survey doesn’t pause a workflow, but Usertick warns that its conditions may match differently.
When someone deletes the survey, its workflows pause with Its survey was deleted. To use one again, choose another survey in its trigger and publish it. Last modified on November 15, 2026