Test, observe, and troubleshoot workflows
26R1 reference · Documentation-based tutorial draft · Not executed in IFS
Use three layers of evidence
Section titled “Use three layers of evidence”| Layer | Question answered |
|---|---|
| Designer validation | Is the model acceptable to the validators? |
| Inspect / Troubleshoot | Which path executes for these supplied inputs? |
| Real trigger with intended role | Does the configured business operation behave correctly? |
Passing one layer does not prove the others. Record the target release and active version with each test result.
Inspect a small case
Section titled “Inspect a small case”Open the diagram and use Inspect. Supply the minimum inputs needed for one path. Review the execution eye icons and variable values immediately before and after the task under investigation.
Save inspection inputs with the tool’s Save feature when useful; its downloaded info.json can be loaded later. Redact real personal or business data before sharing it.
For loops, inspect a small collection and use iteration navigation. The first red error marker helps locate the failing task. Do not increase the debug timeout before checking input volume and repeated calls.
Capture actual trigger inputs
Section titled “Capture actual trigger inputs”- Select the deployed workflow and start Watch.
- Trigger the business operation as the same user.
- Open the captured observation and inspect its source and values.
- Load the observation into Troubleshoot.
- Stop Watch when finished.
The documented watch window is 15 minutes. Another user’s execution is not captured by your watch request. Event values, projection values, and command payloads can differ; capture the actual path you intend to support.
Know what inspection can change
Section titled “Know what inspection can change”Troubleshoot is not a universal sandbox. REST calls run and their target-side changes persist. APIs containing autonomous transactions can also retain side effects, and AI tasks consume tokens.
Use controlled records and endpoints. Before replaying a captured write, understand whether it would duplicate a prior business effect.
Debug input inference can also change enums into strings. If a gateway differs between Inspect and the real trigger, compare types as well as printed values.
Trace the request and async outcome
Section titled “Trace the request and async outcome”Enable the IFS Cloud Web devtools link and use the supported extension. In the request’s Trace view, filter the Workflow category to see triggering process keys, types, timings, and sources.
An asynchronous POSTED trace records queueing, not the later execution outcome. Inspect the asynchronous execution page and error history for completion.
Minimum test suite
Section titled “Minimum test suite”Use the workflow test matrix: happy path, missing and boundary values, empty collections, wrong role, no matching record, stale ETag, cancellation, repeated invocation, external failure, queued-version changes, and realistic volume.
For every case record both the displayed outcome and persisted data. “No error appeared” is not a sufficient expected result.
Finish by testing the packaged configuration in a second environment; that exposes missing triggers, grants, configuration keys, and secrets.