Product
Run history: see every decision your systems asked for
Every call to a Condexa decision is now recorded with its inputs, outputs and trace, so you can answer why the system said that, months later.
The Condexa team · · 2 min read
A decision you cannot explain is a decision you cannot defend. When a customer disputes a credit refusal, or an auditor asks why an order went straight through, you need more than "that is what the system said".
Run history gives you the answer.
What is recorded
Every time an application calls a Condexa decision, the run is kept with:
- The inputs that were sent
- The outputs that came back
- The full trace: every step, every lookup, every value and how long it took
- The version of the workflow that answered
You can browse the list of recorded runs and open any one to see exactly how the answer was reached.
Why it matters
- Audit questions take minutes, not days. Find the run and show the trace.
- Disputes become simple. You can see the facts the decision used on the day.
- Rule changes are safer. Compare how a decision behaved before and after a new version went live.
- Every caller is visible. Calls are made with an API key issued to a named application, so you know which system asked.
Run history works alongside the test trace you use before publishing. Test tells you how a rule should behave; run history shows how it did.
Read more about the decision trace and versioning, or see run history in a 30-minute demo.