Run and Debug Ingestion Workflows
Learn how to run, debug, troubleshoot, and monitor ingestion workflows in Sprinto using execution controls, troubleshooting tools, run history, and revision history.
After creating an ingestion workflow, you can run and troubleshoot it directly from the plan overview page.
Sprinto provides execution and debugging tools that help you:
Run workflows manually
Troubleshoot workflow issues
Validate ingestion logic
Review execution history
Monitor workflow activity
Restore previous workflow versions
These tools help ensure ingestion workflows run successfully before moving into production use.
Before You Begin
Ensure that:
An ingestion plan already exists
Required credentials are attached
Providers are configured correctly
Workflow configuration has been reviewed
Open the Plan Overview
To manage workflow execution:
Log in to the Sprinto dashboard.
Go to Ingestion.
Open the Plans tab.
Locate the required plan.
You can open the workflow overview using either:
Detailed from the three-dot menu
The workflow drawer for template-based plans
Run a Workflow
Running a workflow executes all configured ingestion steps.
Run the Workflow
Open the required workflow.
Click Run.
Configure the execution settings.
Click Run Plan.
Sprinto begins processing the ingestion workflow immediately.
Configure Execution Settings
Before execution starts, Sprinto displays additional run options.
Disable Cache
Enable Disable Cache to force Sprinto to retrieve fresh data instead of using cached responses.
Use this when:
Testing updated integrations
Reviewing recent API changes
Troubleshooting stale results
Verbose Logging
Enable Verbose Logging to generate detailed execution logs.
Verbose logs help when:
Investigating failures
Reviewing workflow behaviour
Inspecting step execution
Review Workflow Status
After execution starts, Sprinto updates the workflow status automatically.
Execution outcomes may include:
Successful execution
Failed execution
Validation errors
Partial processing
Workflow behaviour depends on:
Workflow configuration
Provider connectivity
Credentials
API responses
Step logic
Troubleshoot a Workflow
Use Troubleshoot to validate or debug workflows before production execution.
Troubleshooting provides additional controls that help test workflow behaviour safely.
Open Troubleshoot
Click Debug to open the required workflow.
Sprinto opens the troubleshooting modal.
Configure Troubleshooting Options
The troubleshooting modal includes additional execution controls.
Commit Data
Enable Commit Data to save records created during troubleshooting.
Disable this option when testing workflows without storing output.
Disable Cache
Enable Disable Cache to ignore cached responses during troubleshooting.
This helps validate fresh processing behaviour.
Select a Troubleshooting Scope
Sprinto supports multiple troubleshooting scopes.
Entire Workflow
Runs the complete ingestion workflow.
Use this to validate full workflow behaviour.
Single Step
Runs one specific workflow step.
Use this when troubleshooting:
API requests
Transformations
Processing conditions
Entity insertion
Run a Single Step
Select Single Step.
Choose the required step.
Start troubleshooting.
Range of Steps
Runs a selected portion of the workflow.
Use this when validating part of the ingestion pipeline.
Run a Step Range
Select Range.
Select the starting step.
Select the ending step.
Click Debug Run to start troubleshooting.
Review Steps
The Steps section displays all workflow steps included in the plan.
This helps you understand:
Step order
Workflow behaviour
Processing flow
Execution dependencies
You can review workflow structure before troubleshooting.
Review Run History
Run History displays previous workflow executions.
Use Run History to:
Review workflow activity
Investigate failures
Track execution duration
Review previous runs
Open Run History
Open the required workflow.
Click Run History.
Sprinto displays all recorded executions.
Understand Run History
Each execution may include:
Status
Execution outcome
Started At
Workflow start time
Duration
Total execution time
Version
Workflow version used
Actions
Opens execution details
View Execution Details
Execution details provide deeper visibility into workflow behaviour.
Open Execution Details
Open Run History.
Locate the required execution.
Click View.
Sprinto opens the execution details drawer.
Review Execution Information
Execution details may include:
Workflow timeline
Step execution progress
Runtime metadata
Error messages
Processing logs
Timeline View
The execution timeline helps identify where processing stopped.
Typical statuses include:
Scheduled
Started
Running
Completed
Failed
Review Revision History
Revision History tracks workflow changes over time.
Each saved change creates a new revision entry.
Use Revision History to:
Review workflow changes
Compare versions
Restore earlier configurations
Open Revision History
Open the required workflow.
Click Revision History.
Sprinto displays all saved revisions.
Compare Workflow Versions
Revision comparison helps identify workflow changes between saves.
Comparison views may include:
YAML comparison
JSON comparison
Highlighted configuration changes
You can review:
Added workflow steps
Removed configuration
Updated parameters
Modified logic
Restore a Previous Version
Rollback restores an earlier workflow revision.
Use rollback when:
Recent changes introduced issues
Workflow behaviour must be restored
A stable configuration is required
Restore a Workflow Version
Open Revision History.
Locate the required revision.
Click Rollback to this version.
Confirm the action.
Sprinto restores the selected workflow version.
Use Additional Workflow Actions
Additional workflow actions are available from the three-dot menu next to each workflow.
Available actions include:
Detailed
Opens the workflow overview page
Edit
Opens Visual Editor or YAML Editor
AI Editor
Opens the conversational workflow editor
Delete
Removes the workflow
Delete or Mark a Workflow Inactive
Deleting a workflow permanently removes the configuration.
Before deletion, Sprinto allows you to:
Confirm deletion
Mark the workflow as inactive instead
Marking a workflow inactive disables execution without permanently removing the workflow.
When to Troubleshoot Workflows
Troubleshooting is recommended when:
A workflow fails unexpectedly
API responses change
Entity records are not appearing
Workflow logic was recently updated
Credentials were modified
New processing steps were added
Use Troubleshoot before production execution whenever possible.
Best Practices
Use the following recommendations when running ingestion workflows:
Review execution steps before running workflows
Use Troubleshoot before production execution
Enable Verbose Logging when debugging
Disable cache when validating recent updates
Review Run History regularly
Use Revision History before major changes
Restore stable versions when troubleshooting configuration issues
Related Topics
Last updated