OS UniversityOS University™
    LibraryAutomationsTroubleshooting Workflows

    Troubleshooting Workflows

    Module: Automations • 5:01

    Overview

    Before you publish a workflow to everyone, you should test it end-to-end with a real contact. This lesson shows how to trigger a workflow using a tag (the easiest way to test hard-to-simulate triggers like payments or opportunity changes), then verify every action fired correctly using Enrollment History, Execution Logs, and the Contact Execution Path visualizer.

    Step-by-Step Instructions

    1

    Add a wait step at the bottom

    Open your workflow and place a wait step at the very end so test contacts pause instead of falling out of the workflow while you inspect results.

    2

    Use a tag to trigger the test

    For triggers that are hard to simulate (payments, invoices, opportunity changes, contact updates), set the trigger to 'Tag Added' and add a test tag like 'test' to a real contact. For form-triggered workflows you can also just submit the live form.

    3

    Add the tag to a test contact

    Go to Contacts, open a test contact (e.g. Nicole), add the test tag, and hit apply. The contact will enter the workflow immediately.

    4

    Check Enrollment History

    Back in the workflow, open Enrollment History. You'll see the contact's name, enrollment reason, date enrolled, current action, status (e.g. 'waiting for time'), and next execution time.

    5

    Open Execution Logs

    Click into the execution to view every action that ran — added to workflow, created/updated opportunity, sent email, etc. Successful actions show green; errors show red. You can view details, go to the contact, or go to the action from here.

    6

    Use the Contact Execution Path

    For workflows with multiple if/else branches, the Contact Execution Path highlights (green, pulsing) the exact trigger entry point and every action the contact passed through, plus the action they're currently on — the easiest way to trace a complex journey.

    7

    Verify the results on the contact

    Refresh the contact record to confirm the tag was added, then check Pipelines → View to confirm they were placed in the right stage and marked correctly (e.g. won/closed). Open any sent email/SMS to confirm it delivered.

    8

    Prefer live testing over the Test Workflow button

    The built-in 'Test Workflow' feature sometimes doesn't send emails/texts properly. Running it live via a contact tag gives you accurate, real-world results before you publish to everyone.

    Common Mistakes

    • Forgetting to save changes before navigating away.
    • Not testing the configuration after setting it up.
    • Skipping the prerequisites mentioned in the overview.

    Action Checklist