Skip to main content

Reports

Reports show you what happened when a workflow ran -- which nodes executed, what data flowed through them, and whether anything failed.

Types of reports​

Orqio provides two levels of reporting:

Workflow execution report​

A workflow execution report shows the full picture of a single workflow run:

  • Status -- whether the workflow completed successfully, failed, or is still running
  • Timeline -- when the workflow started and how long each step took
  • Trigger data -- the input that started the workflow
  • Node sequence -- which nodes ran and in what order

You can find workflow execution reports in the Executions section of the Orqio app.

Node execution report​

Each node within a workflow run has its own report with:

  • Input -- the data the node received
  • Output -- the data the node produced
  • Status -- whether the node succeeded or failed
  • Duration -- how long the node took to execute
  • Delivery status -- for message nodes (email, SMS), whether the message was sent, delivered, or failed (see Node Configuration)

Click on any node in the execution timeline to see its detailed report.

Reading an execution report​

When you open an execution from the Executions list:

  1. Check the overall status -- did the workflow complete or fail?
  2. Find the failing node -- if the workflow failed, the timeline shows which node caused the issue
  3. Inspect inputs and outputs -- check what data each node received and produced
  4. Review delivery status -- for message nodes, confirm that messages were sent successfully
  5. Check timing -- identify slow nodes that might need optimization

Common scenarios​

Debugging a failed workflow​

  1. Open the failed execution in Executions
  2. Look for the node marked as failed
  3. Check the node's input -- was it missing data or receiving unexpected values?
  4. Check the node's error message -- it often explains what went wrong
  5. Fix the issue in the blueprint, run once again, and verify

Verifying message delivery​

  1. Open the execution report
  2. Find the delivery node (Send Email, Send SMS, etc.)
  3. Check the delivery status: Sent, Delivered, Failed
  4. If failed, check the error for details (invalid address, provider issue, etc.)

Monitoring production workflows​

Review execution reports regularly to:

  • Spot recurring failures before they become problems
  • Verify that workflows complete in expected timeframes
  • Confirm that messages are being delivered successfully
  • Identify patterns in trigger data that might require blueprint adjustments

Best practices​

  • Check reports after publishing. Review the first few production executions to confirm everything works.
  • Investigate failures promptly. A failed node often indicates a configuration issue or an upstream data problem.
  • Use Run once for testing. It creates a real execution report you can inspect, just like a live run.
  • Monitor delivery status. Don't assume messages were delivered -- check the delivery status in the report.