# Debugging & Testing

Ondeva gives you **real-time visibility** into your workflow’s execution. Whether you're saving data, calling APIs, or processing conditions — you can simulate, inspect, and troubleshoot logic directly in the builder without deploying first.

No more blind spots. No more “why didn’t this run?”

### **How to Run a Workflow for Debugging**

In the Workflow Builder top bar, you’ll find the **Execute** button.

#### **Execute (Test Run)**

* Executes your workflow **immediately** from start to finish using current session state
* No trigger required — even event-based workflows can be run this way
* Results and logs are shown live inside the browser console.

***

### **Debugging Tools & Features**

#### Monitoring

Each action execution is logged in the monitoring area of the platform. You can see the log for each executed workflow there. Logs are cleared after 1h.

#### **API Response Handling**

In [Call API](https://docs.ondeva.com/steps-reference/logic#call-api) steps:

* You can store the raw response in a variable
* Test runs show actual response content
* Errors (e.g. bad auth, invalid body) are surfaced immediately

#### **Isolated Workflow Runs**

* You can test subflows ([Execute Workflow](https://docs.ondeva.com/steps-reference/logic#execute-workflow)) independently
* Parameters from the parent are passed through — but you can simulate local overrides

***

### Debugging Tips

* Store **API results** into session variables to inspect them mid-flow
* Use **invert condition checkboxes** to test both true/false logic quickly
* Use **Remove Session Parameter** at the start of your workflow to clear stale state
* Label branches and comments using workflow step names to stay organized

***

### Publishing vs. Testing

* **Execute** is for **local test runs** — nothing is made live
* **Publish** makes the workflow available to triggers (form, button, time-based)
* Use Execute to **verify behavior before enabling triggers**