Testing and Debugging

Before publishing a workflow to production, thorough testing ensures it behaves correctly under various conditions. The Workflow Builder provides tools to execute workflows, monitor progress, and diagnose issues.

Test Execution

Starting a Test Run

To test your workflow:

1. Click the Play button in the toolbar at the top of the canvas
2. The execution form appears, displaying all input variables defined for your workflow
3. Fill in the required values for each input variable
4. Click Execute to start the test run

The Execution Form

The execution form is generated automatically from your workflow's input variables:

• Required fields are marked and must be filled before execution
• Optional fields with default values are pre-populated
• Field types determine the input control (text, number, dropdown, etc.)
• Descriptions appear as help text below each field

After clicking Execute, the workflow begins running and you can monitor its progress directly on the canvas.

Real-time Status

Visual Execution Feedback

During execution, each node on the canvas displays its current status through colored borders:

The animated blue border pulses to indicate active processing, making it easy to track which task is currently running.

Watching Execution Progress

As your workflow executes:

1. Tasks turn blue one by one as they begin execution
2. Successfully completed tasks turn green
3. Failed tasks turn red, and execution may stop depending on error handling configuration
4. You can follow the flow of execution visually across the canvas

Viewing Logs

Accessing Task Logs

To view detailed logs for any task:

1. Click on the task node in the canvas
2. The Properties Panel opens on the right side
3. Navigate to the Logs tab

Log Information

The Logs tab displays:

• Execution timestamp: When the task started and completed
• Input values received: The actual data passed to the task
• Output values produced: The data returned by the task
• Error messages: Detailed error information if the task failed
• Execution duration: How long the task took to complete

Reading Error Messages

When a task fails, the error message typically includes:

• Error type: The category of error (validation, connection, timeout, etc.)
• Error details: Specific information about what went wrong
• Stack trace: Technical details for debugging (more useful for developers)

Previewing Outputs

The Preview Tab

The Preview tab shows the output data from the most recent execution:

1. Select a task on the canvas
2. Open the Properties Panel
3. Click the Preview tab

Understanding Output Data

The preview displays:

• JSON view: The complete output data in JSON format
• Expandable sections: Nested objects can be expanded to explore the data structure
• Value types: Data types are indicated for each field

This is particularly useful for:

• Verifying that a task returns the expected data structure
• Understanding what fields are available for use in subsequent tasks
• Confirming that variable mappings are working correctly

Debugging Tips

Start Simple

When building a new workflow:

1. Add one or two tasks at a time
2. Test after each addition
3. Verify outputs before connecting more tasks
4. Build complexity gradually

This incremental approach makes it easier to identify which change introduced a problem.

Test After Each Task

Rather than building the entire workflow before testing:

1. Add a task
2. Configure its inputs
3. Run a test execution
4. Check the output in the Preview tab
5. Only then proceed to the next task

Check Variable Mappings

Most workflow errors stem from incorrect variable mappings:

1. Open the task's Advanced tab
2. Review each input mapping
3. Verify variable names are spelled correctly
4. Check that paths to nested properties are accurate
5. Use the variable picker to avoid typos

Use Comment Tasks

For complex workflows, add Comment tasks to document your logic:

• Explain why certain decisions are made
• Note expected values at different points
• Mark sections that require special attention
• Leave reminders about edge cases

Review Execution Order

Verify that tasks execute in the correct order:

• Check connections between tasks
• Ensure dependencies are properly defined
• Verify that parallel branches merge correctly
• Confirm that conditional logic follows the expected paths

Common Error Messages

Errors are a normal part of building workflows. When something goes wrong, the system shows you a message explaining what happened. Here are the most common errors you might see and how to fix them.

"Missing required input variable"

What you see: An error mentioning a missing variable, like borrower_id.

What this means: The workflow needs a piece of information to run, but that information was not provided. Think of it like a form asking for your email address but you left it blank.

How to fix it:

1. Go back to the execution form (when you click Play)
2. Look for any empty fields that should have values
3. Fill in the missing information and run again

"Cannot resolve variable path"

What you see: An error saying a variable path could not be found, sometimes showing what you typed and what options are actually available.

What this means: The workflow is looking for data in a specific location, but it cannot find it. This usually happens because of a typo. For example, you might have typed scroe instead of score.

How to fix it:

1. Click on the task that failed
2. Open the Advanced tab in the Properties Panel
3. Check the variable names in your mappings
4. Use the variable picker (the dropdown that shows available variables) to select the correct option instead of typing manually

"Failed to connect to external service"

What you see: A connection error mentioning a URL or external service.

What this means: The workflow tried to reach another system (like a credit bureau or data provider) but could not connect. This is often temporary.

How to fix it:

1. Wait a moment and try running the workflow again
2. If it keeps failing, the external service might be down - try again later
3. Double-check that the URL in your task configuration is correct

"Task execution exceeded time limit"

What you see: A timeout error indicating the task took too long.

What this means: The task was waiting for a response but it took longer than allowed. This can happen when external services are slow or when requesting large amounts of data.

How to fix it:

1. Click on the task that timed out
2. Open the Advanced tab
3. Look for the timeout setting and increase it (try doubling it)
4. Run the workflow again
5. If it still times out, the external service may be experiencing issues

"Expected number but received string"

What you see: A type mismatch error, often mentioning what was expected versus what was received.

What this means: A task expected one type of data (like a number) but got something different (like text). For example, the number 750 and the text "750" look similar but are treated differently.

How to fix it:

1. Click on the task that failed
2. Check the Preview tab of the previous task to see what data it produced
3. If the data looks correct but is the wrong type, add a Transform task before this one to convert the data
4. If you need help with transforms, see the Transform task documentation

Common Issues

Missing Required Inputs

Symptom: Task fails with "missing required input" error

Solutions:

• Open the task's Advanced tab and check all input mappings
• Verify the source variable exists and contains data
• Check for typos in variable names or paths
• Ensure the producing task executed successfully

Connection Errors

Symptom: Task fails with connection or network error

Solutions:

• Verify the external service is available
• Check that authentication credentials are valid
• Review rate limits if making many requests
• Try running the task again (transient network issues)

Timeout Errors

Symptom: Task fails with timeout error

Solutions:

• Increase the task timeout in the Advanced tab
• Check if the external service is responding slowly
• Simplify the request if possible
• Consider breaking into smaller operations

Invalid Data Format

Symptom: Task fails with data validation or parsing error

Solutions:

• Check that input data matches expected types
• Review the data structure in the Preview tab
• Verify date formats, number formats, and string lengths
• Check for null values where data is expected

Conditional Logic Not Working

Symptom: Workflow takes unexpected path at decision points

Solutions:

• Review the condition expression in the decision task
• Check the actual values being compared (use Preview tab)
• Verify comparison operators are correct
• Test with different input values to isolate the issue

Testing Best Practices

Create Test Scenarios

Before testing, prepare scenarios covering:

• Happy path: Normal execution with valid data
• Edge cases: Boundary values, empty fields, maximum lengths
• Error conditions: Invalid data, missing values, service unavailable

Document Test Results

Keep track of your testing:

• Note which scenarios passed or failed
• Record the input values used
• Document any issues discovered
• Mark areas that need additional testing

Test Before Publishing

Always run a complete test before publishing:

1. Execute the workflow with representative test data
2. Verify all paths through the workflow
3. Check that outputs contain expected values
4. Confirm error handling works correctly