Automate Everything | Entry 86
Workflow logs replace guesswork with evidence. HubSpot's Workflow Details page, action logs, issue reviews, enrollment history, record testing, revision history, connections, and visual record paths help nonprofit teams diagnose why an automation succeeded, failed, skipped a step, or produced an unexpected CRM update.
A nonprofit can begin with a broad review of workflow activity or investigate one specific constituent, donation, membership, ticket, registration, or other CRM record.
HubSpot may successfully add every donor to a SYBUNT segment because that is exactly what the workflow was configured to do. In that case, the execution succeeded, but the workflow logic was wrong.
Effective troubleshooting distinguishes execution errors, enrollment problems, configuration mistakes, data-quality issues, integration failures, and conflicts with other workflows.
The available evidence helps the team move from guessing to structured troubleshooting.
The page can reveal global patterns such as an enrollment decline after a revision, repeated failures at one action, an integration that began returning errors, records no longer reaching a branch, or a scheduled workflow enrolling more records than expected.
| Question | Possible evidence |
|---|---|
| Did the action run? | Send, task, update, assignment, integration, delay, skip, or error event |
| Which record was affected? | Record identity and the time the action ran |
| Why did it fail? | Missing values, invalid formats, unavailable owners, app errors, limits, or loop prevention |
| Where is the fix? | The workflow, CRM record, connection, property, association, or underlying process |
Action logs establish what the workflow attempted and whether the step completed.
Authorized users can identify workflows where records encountered problems, open the workflow or record, and decide how the issue should be handled.
Notes can explain temporary outages, incomplete records, expected exceptions, workflow revisions, monitoring decisions, and reasons the team chose not to change an automation.
Filter by date, workflow version, and steps reached. This helps explain differences caused by later exclusions, changed branch criteria, shorter delays, added or removed messages, activation choices, or new property logic.
Enrollment testing can show which part of the criteria a specific record failed to meet.
The gift exists, but the donor never entered the acknowledgment automation. The cause could be an exact-status mismatch, missing donor association, object mismatch, activation timing, disabled re-enrollment, suppression, integration timing, the wrong property, or immediate unenrollment.
Records suddenly stop updating in a connected application. Possible causes include expired authorization, a removed connection, password or permission changes, lost user access, API limits, missing fields, rejected values, failed webhooks, or an unavailable integration action.
A workflow should create memberships after completed payments, but some records are missing or lack associations. The create-record action may have failed, used the wrong object, lacked a source value, skipped the association step, followed another branch, or been changed while records were active.
A workflow incorrectly classifies many constituents as “some year but unfortunately not this year.” Possible causes include the wrong giving property, incomplete imports, missing donation associations, incorrect AND/OR logic, blank dates, calculation timing, a wrong date range, activation enrollment, another workflow clearing a field, or unrecognized household giving.
| Investigate | Correct |
|---|---|
| Review enrollment history and workflow version, test representative records, inspect donation data and associations, check property history and AND/OR logic, and compare import timing with execution. | Pause the workflow, correct the logic, identify affected records, prepare a reviewed correction, test a limited set, and monitor before expanding. |
HubSpot can provide a workflow property-restoration process for eligible changes, allowing an authorized user to select the responsible workflow, affected objects, a qualifying timeframe, and a preview.
Restoration may not reverse changes from another workflow, custom code, activity outside the allowed period, unsupported actions, or downstream effects. Restoring a SYBUNT field will not unsend email, delete tasks, reverse app updates, or undo changes made by a second automation.
The record path can show successful actions, errors, branches, skipped steps, delays, endpoints, and timing.
If a member receives a lapsed-membership email after renewing, the path may show that the workflow waited seven days, evaluated the renewal field before the payment integration updated it, followed the not-renewed branch, and sent the email. The problem may be timing rather than branch logic.
The workflow visible today may not be the version that processed the record last month. Always compare enrollment date, active version, historical property values, and later changes.
A workflow may depend on a segment maintained elsewhere, a form that sets the enrollment property, an integration that creates a record, an email suppression rule, a campaign audience, or another automation that controls unenrollment.
A successful record becomes a baseline. When something fails later, compare the two paths to identify where the data, timing, association, or version diverged.
| Global review | Individual review |
|---|---|
| Sudden increase in errors | Why did this donor receive the email? |
| Decline in enrollments | Why did this member not renew correctly? |
| Action failing across records | Why was this volunteer not assigned? |
| Integration stopped at one time | Why did this registration follow the wrong branch? |
| One version changed outcomes | Why did this record fail or leave immediately? |
The global view shows whether the issue is systemic. The individual view shows exactly how the automation behaved for one record.
Current troubleshooting capabilities can include action logs, enrollment history, issue review, enrollment testing, record-path visualization, revision history, performance information, connections, issue notes, filtering, eligible exports, property restoration, and manual enrollment or unenrollment.
Availability varies by subscription, workflow and export permissions, object access, workflow type, connected apps, and account configuration. Detailed activity follows HubSpot's current retention rules and system limits.
HubSpot's logs and histories help nonprofit teams understand how records entered, which actions ran, where errors occurred, which version was active, and why records followed specific paths.
Teams that routinely review successful and unsuccessful activity can diagnose problems faster, correct affected records more safely, and manage automation with greater confidence.