Flow.Documentation
BeginnerRPA screenshots

Runs and problems

9 steps± 6 minVideoVerified 22 Oct 2026
  1. Step 1 · Open your development environment
  2. Step 2 · Create a workflow with sample data
  3. Step 3 · A rule — with a typo
  4. Step 4 · Two ends and the connections
  5. Step 5 · Look under Problems
  6. Step 6 · Run anyway
  7. Step 7 · Read back what happened
  8. Step 8 · Fix the rule
  9. Step 9 · Save and run again

Everyone makes a typo now and then. Flow helps you find it: Problems lists what is already wrong right now, and Runs tells you for every run what went in, what came out and where it went wrong. You build a small workflow with a mistake in it on purpose, see it fail, find out why and fix it.

Watch the whole guide as a video9 steps in one film
Step 1 / 9

Open your development environment

In the portal, under Environments, click Development, and there Open. Flow opens in a new tab.

  1. Click Development
Open your development environment · Click Development
  1. Click Open ↗
Open your development environment · Click Open ↗
Open your development environment · Flow, with the explorer on the left and the module General.
Step 2 / 9

Create a workflow with sample data

A new workflow, with an invoice as its example: a number, a supplier and a total.

  1. Click Add to General
Create a workflow with sample data · Click Add to General
  1. Click New workflow
Create a workflow with sample data · Click New workflow
  1. In Workflow name, type Check an invoice
Create a workflow with sample data · In Workflow name, type Check an invoice
  1. Click the trigger
Create a workflow with sample data · Click the trigger
  1. Click Code
Create a workflow with sample data · Click Code
  1. In the sample data, type {"invoice": "F-2026-014", "supplier": "Van Dijk Printing", "total": 1250}
Create a workflow with sample data · In the sample data, type {"invoice": "F-2026-014", "supplier": "Van Dijk Printing", "total": 1250}
Step 3 / 9

A rule — with a typo

Add an If / Else that checks whether the invoice is over 1000 euros. We type the wrong field on purpose: amount instead of total. Exactly the kind of mistake that happens for real.

  1. Click Add node
A rule — with a typo · Click Add node
  1. Click If / Else
A rule — with a typo · Click If / Else
  1. In Name, type Over 1000?
  2. In Which field to check?, type amount
  3. In **Comparison Equals Does not equal Is greater than Is greater than or equal to Is **, choose Is greater than
  4. In Value, type 1000
A rule — with a typo · In Name, type Over 1000?; In Which field to check?, type amount; In **Comparison Equals Does not equal Is greater than Is greater than or equal to Is **, choose Is greater than; In Value, type 1000
Step 4 / 9

Two ends and the connections

Over 1000 the invoice goes for approval, otherwise it is paid straight away. Add End twice, name them and connect trigger → rule, Yes → for approval and No → pay straight away.

  1. Click End
Two ends and the connections · Click End
  1. In Name, type For approval
Two ends and the connections · In Name, type For approval
  1. Click End
Two ends and the connections · Click End
  1. In Name, type Pay straight away
Two ends and the connections · In Name, type Pay straight away
  1. Click Fit to view
Two ends and the connections · Click Fit to view
  1. Click Event trigger
Two ends and the connections · Click Event trigger
  1. Click Over 1000?
Two ends and the connections · Click Over 1000?
  1. Click Over 1000? — Yes
Two ends and the connections · Click Over 1000? — Yes
  1. Click For approval
Two ends and the connections · Click For approval
  1. Click Over 1000? — No
Two ends and the connections · Click Over 1000? — No
  1. Click Pay straight away
Two ends and the connections · Click Pay straight away
  1. Click Save
Two ends and the connections · Click Save
Step 5 / 9

Look under Problems

At the bottom is the Problems tab, with a number when something is wrong. Flow looks along while you build: the field the rule checks does not exist in the data. The step itself also gets a red exclamation mark.

  1. Click PROBLEMS1
Look under Problems · Click PROBLEMS1
Look under Problems · ‘Over 1000?’ checks amount, but that field does not exist at this point.
Step 6 / 9

Run anyway

Click Run. Flow first asks whether you are sure, because the workflow will probably fail. We do it anyway, to see what a failed run looks like.

  1. Click Run
Run anyway · Click Run
  1. Click Run
Run anyway · Click Run
Run anyway · Status: Failed.
Step 7 / 9

Read back what happened

Click Run in the bar on the left, then Runs and the run. You see the input, the output, every step and the error: the field is missing. That is also how you find out later what happened with a real request.

  1. Click Runs
Read back what happened · Click Runs
  1. Click Runs
Read back what happened · Click Runs
  1. Click the failed run
Read back what happened · Click the failed run
Read back what happened · The error: Field missing: amount.
Step 8 / 9

Fix the rule

Open workflow takes you back to the canvas. Click the rule and change the field to total. Under Problems the message is gone straight away.

  1. Click Open workflow ↗
Fix the rule · Click Open workflow ↗
  1. Click Over 1000?
Fix the rule · Click Over 1000?
  1. In Which field to check?, type total
Fix the rule · In Which field to check?, type total
  1. Click PROBLEMS
Fix the rule · Click PROBLEMS
Fix the rule · No problems found.
Step 9 / 9

Save and run again

Now the run succeeds: the total is 1250, so the invoice goes for approval. The failed run simply stays in Runs — history is never rewritten.

  1. Click Save
Save and run again · Click Save
  1. Click Run
Save and run again · Click Run
Save and run again · Status: Completed.
Save and run again · total gt 1000 → TRUE: the invoice goes for approval.

This guide was carried out step by step on 22 Oct 2026 by an automated test on Flow (version 3e563176).