Test a Workflow Safely v2

Test the smallest useful behavior in the Test Environment.

Choose the right test mode

Mode Use it for Important boundary
Designer Debug Current unsaved or saved design with real Node invocation Uses the injected design; default execution limit is five minutes.
Published invocation Trigger, routing, authorization, status, and released-artifact checks Runs the artifact published to the selected Environment.

Use Activation Modes and Timeouts for the complete behavior differences.

Prepare a controlled test

  1. Work in the Test Environment.
  2. Confirm the selected Cluster and the Environment values of every Connection.
  3. Choose representative input with a small record count.
  4. Limit any query, page size, date range, or mutation scope.
  5. Identify the expected output and external changes before running.

Use test accounts, folders, queues, recipients, or records where the provider supports them. Do not assume that Debug suppresses a Node's real side effects.

Validate before running

Resolve blocking messages in Problems. Inspect mapping results in Preview, then verify:

  • Required Parameters have Values or Expressions.
  • Connection keys are selected rather than invented.
  • The Workflow and Connections use compatible Cluster placement.
  • The correct Environment is selected.
  • Trigger-specific receive/respond structure is valid when testing publish.

Run and inspect

  1. Click Run for a designer Debug.
  2. Provide Workflow Parameter values when prompted.
  3. Follow the live rows in Logs.
  4. Inspect each relevant Step's actual inputs, Returns, duration, and error.
  5. Confirm the Workflow Return.
  6. Verify the external system for the exact expected side effect.

Use Run this step or Run to this step only when the selected slice has all required upstream state and its side effects are safe. A partial run is not evidence that the complete Workflow ordering and error path work.

Test failure paths

Exercise invalid input, empty results, provider rejection, and the intended recovery route. Confirm that TryCatch handles only errors you mean to recover from and that Finally behavior is safe.

Stop requests and timeout cancellation are cooperative. A Node or external operation can take time to observe cancellation, so verify the final log state rather than assuming an immediate stop.

Verify the released artifact

After saving and publishing:

  1. Confirm the intended revision in Release Management.
  2. Confirm the Workflow is Enabled in the target Environment.
  3. Invoke it through the actual published interface with a non-destructive test case.
  4. Confirm authorization, hostname, route, response, and logs.

See also

See Workflow Status, Revisions and Releases, and Workflow Designer.