Overview
Every time an automation fires in Wedy Pro, it creates a run — a live record of that automation executing in a specific lead or project. The Activity tab on the Automations page is your central dashboard for tracking every run across your entire business: what's in progress, what completed successfully, what's waiting for your approval, and what failed.
Checking the Activity tab regularly — especially before an event date — gives you confidence that the right emails went out, the right tasks were created, and your client experience is running on schedule.
Time to complete: 5–10 minutes to review and act on your activity log.
How to access the Activity tab
To open the automation run history in Wedy Pro:
Navigate to Automations in the sidebar.
Click the Activity tab at the top of the page (next to the Automations tab).
The Run history section loads, showing all runs sorted by most recent first.
What an automation run is
An automation run is a single instance of an automation firing. Each time the trigger condition is met — for example, a new lead form submission or a project stage change — the automation starts a new run for that specific lead or project. A single automation can generate hundreds of runs over time, one per triggering event.
For example: if your Lead Form Submitted automation fires every time an inquiry comes in, each new inquiry creates its own run. The Activity tab shows all of these runs side by side so you can see which ones completed, which are still in progress, and which encountered an issue.
Reading the run history
The Run history section displays your runs in card view by default. You can switch to table view using the layout toggle on the right. Each run entry shows:
Automation — the name of the automation that fired
Project — the lead or project the run is associated with
Status — the current state of the run (see below)
Current Step — the node the run is currently at or last completed
Started — the date and time the run began
Understanding run statuses
Every run in the Activity tab has one of the following statuses:
In Progress — the run is actively executing. This includes runs that are currently processing a step, waiting on a delay, or waiting for a condition to be met.
Approval Required — the run has reached an action configured to require your manual approval before it executes. You must approve or reject the pending action from the run detail view.
Completed — all steps in the automation finished successfully. No further action needed.
Failed — the run encountered an error and could not complete. Common causes are listed below in the troubleshooting section.
Cancelled — the run was stopped manually before completing.
Expired — the run timed out, typically when a Wait Until Event delay reached its maximum wait time without the expected event occurring.
Filtering and searching runs
If you manage multiple automations and clients, the Activity tab can grow quickly. Use the filter dropdowns to narrow down what you see:
Status filter — filter by All Status, In Progress, Approval Required, Completed, Failed, or Cancelled to focus on the runs that need attention
Automation filter — show runs from a single specific automation (e.g., only your inquiry welcome automation)
Project filter — show all runs associated with a specific client project or lead
To find runs for an upcoming event, use the Project filter and select the client's project. This shows every automation that has run — or is currently running — for that event. For example, a wedding photographer can filter by a couple's project the week before their wedding date to confirm the contract reminder, final payment nudge, and day-before confirmation email all show a Completed status.
Viewing a run's details
To see exactly what happened inside a run — step by step:
From the Activity tab, find the run you want to inspect.
Click the run card, or click the ⋯ menu on the run → View Run.
The run detail view opens — a visual canvas showing the automation flow with execution status badges overlaid on each node.
Each node shows one of the following badges: Completed (green), Waiting (amber), Failed (red), Pending (grey), or Skipped.
Click any node to see its execution details in the floating panel on the right — including when it ran and what it did.
If a run is In Progress, the run detail view auto-refreshes every 10 seconds so you can watch the automation advance in real time.
If a run is waiting on a Wait Fixed Time or Wait Until Event delay and you need to advance it immediately, click Skip Delay in the delay node's panel (a confirmation modal will appear).
Handling runs that require approval
If you have configured any action with Approval Required, the run pauses at that action and shows an Approval Required status in the Activity tab. To handle it:
Open the run detail view by clicking on the run.
A prompt appears in the header indicating a pending action is awaiting approval.
Review the action — for example, a draft email ready to send to a client, or a Move Stage action that would close the project.
Click Approve to allow the action to execute, or Reject to skip it. If you reject, the run stops at that node.
Approval Required is useful for actions like sending a proposal or moving a project to a closed stage — where you want a final manual review before Wedy Pro acts on your behalf.
How to cancel an in-progress run
To stop an automation run before it completes:
In the Activity tab, find the run you want to stop.
Click the ⋯ menu on the run → Cancel Run, or open the run detail view and click Cancel Run in the header.
Confirm the cancellation in the modal that appears.
Important: Cancelling a run stops all remaining steps — not just the current one. Any steps that have already completed (emails sent, tasks created, stages moved) are not reversed. Only pending and future steps are stopped. This action cannot be undone.
Common issues and how to fix them
When a run shows a Failed status, open the run detail view and click the red-badged node to see the specific error. The most common causes and fixes are:
Email account disconnected — A Send Email action failed because your email integration is no longer connected. Fix: go to Account > Integrations, reconnect your email account, then recheck whether the automation needs to be re-triggered for affected clients.
Email template deleted — The email template linked to a Send Email action no longer exists. Fix: recreate the template or edit the automation to select a different template, then save.
Project stage deleted — A Move Stage action references a pipeline stage that has been removed. Fix: edit the automation, update the Move Stage node to select an existing stage, and save.
Smart document template deleted — A Send SmartDocument action references a deleted document template. Fix: edit the automation to select an active template.
Expired run — A Wait Until Event delay reached its maximum wait time without the triggering event occurring (e.g., a client never signed the contract within the configured window). The run expires and stops. This is expected behavior — no fix needed unless you want to adjust the max wait duration in the automation.
Prevent issues before they happen
The best way to avoid failed runs is to treat your automations like any other business tool — review them proactively, not just when something goes wrong.
Before deleting any email template or document template, check whether it is linked to an active automation. Open the automation in the editor and verify no actions reference the template you plan to delete.
Before deleting a pipeline stage, check your automations for any Move Stage actions that target it.
Before a major event date, filter the Activity tab by the client's project. Confirm that expected runs — welcome email, contract reminder, payment receipt confirmation — show a Completed status. If anything shows Failed or is still In Progress when it should have completed, investigate and follow up with the client manually if needed.
After setting up a new automation, use the Test Run button in the automation editor to simulate the flow without affecting real clients. Then check the Activity tab to verify each step executed as expected before activating the automation for live use.
Keep your email integration active. All automation-triggered emails are sent through your own connected email account. If the connection lapses, email actions will fail silently. Check your integration status under Account > Integrations periodically.
Frequently asked questions
Can I see runs from all automations in one place?
Yes. The Activity tab shows runs from every automation you have created, across all leads and projects. Use the filters to narrow by automation name, project, or status.
What happens to in-progress runs when I deactivate an automation?
Deactivating an automation stops new runs from starting — it does not cancel runs that are already in progress. Existing in-progress runs will continue executing their remaining steps. To stop them, you need to cancel each run manually from the Activity tab.
What happens to in-progress runs when I edit and save an active automation?
When you save changes to an active automation that has in-progress runs, Wedy Pro shows an Active Runs modal. You can choose either Duplicate and Save (the existing runs continue under the old version of the automation) or Cancel Runs and Save (all in-progress runs are immediately stopped). Choose based on whether you want the in-flight runs to complete their original flow or be stopped.
Does cancelling a run undo the steps that already ran?
No. Cancelling a run stops all pending and future steps, but any actions that have already executed — emails sent, tasks created, stages moved — remain in place. There is no rollback.
How long does run history stay in the Activity tab?
Run history is kept indefinitely, so you can audit past automation activity at any time. Filter by project to see a full record of every automation that has ever fired for a specific client.
Can I re-run a failed automation for a specific client?
There is no one-click re-run for a failed run. To retry, fix the underlying issue (reconnect email, restore the template, etc.), then manually trigger the automation again — for example, by moving the project to the relevant stage or sending the document that serves as the trigger. Alternatively, complete the missed steps manually (send the email directly, create the task yourself) and move forward.
Related articles