# Workflow Activity and testing

Inspect runs, distinguish waiting from failure, and diagnose a workflow without repeating unwanted actions.

## Inspect a run

Open **Workflow Activity** and find the workflow and time you tested. Inspect its status and available step details. The question to answer is: did the expected event start the workflow, and how far did it get?

Run statuses distinguish active work, waiting, completion, and failure. A run waiting at Receive Message may simply need the next customer reply. A pending ChatGPT Task can be waiting for its result or deadline.

## Test with a small matrix

| Test | What it checks |
| --- | --- |
| Normal input | The main path achieves the intended result |
| Empty or unusual input | Validation and fallback behavior |
| Unavailable account or resource | The error path is connected and useful |
| Repeated event | The task does not create unwanted duplicates |
| Paused optional step | Later steps handle its empty output |
| Fresh conversation vs returning chat | The selected trigger matches the intended situation |

## Inspect before retrying

Check whether a send, insert, or other external action might have completed before the run reported a problem. Inspect the destination when needed. Repeating a whole workflow can repeat earlier successful actions too.

If a run is waiting, identify what it is waiting for before treating it as broken. If you cancel a run through an available application control, that does not reverse actions already accepted by another service.

## Save and test are different

Validation checks the definition. A live test checks behavior with real resources and permissions. Saving successfully does not prove that a recipient exists, a connection can access a file, or an external service will accept the request.

Use test data and a controlled destination, then confirm the actual output before activating a broader workflow.

## Ask for help with useful details

Record the workflow name, trigger type, time of the test, observed status, failed node label, and a concise description of what you expected. Remove credentials, private customer data, and sensitive request content from anything you share.