Errors are a part of scenario execution, and knowing how to handle them is crucial. Learn to navigate errors caused by service failures, unexpected data responses, or input validation issues. Discover how to customize error handling using Boost.space Integrator versatile directives. Explore five key error types, from connection errors to rate limits, and grasp how each impacts scenario execution. Gain the skills to keep your scenarios running smoothly, even in the face of errors.
Boost.space Integrator enables error handling during scenario execution. Error handler routes can be added to modules, allowing customization with directives like Resume, Ignore, Break, Rollback, or Commit, ensuring smooth execution and tailored error management.
Boost.space Integrator lacks the Retry error handling directive, but alternative solutions include using the Break directive with incomplete executions storage or employing the Repeater module to set retry attempts.
Boost.space Integrator lacks the Throw error handling directive, but you can simulate it by configuring a module to optionally fail during its operation, such as the JSON > Parse JSON module. Alternatively, you can use a workaround with the HTTP Module to retry after some time if no record is found, employing the Break Directive for handling errors.
Boost.space Integrator manages various error types during scenario execution, including connection errors, data errors, and rate limit errors. Each error type triggers specific handling mechanisms to ensure smooth scenario operation.
This article delves into advanced error handling techniques, including filtering and nesting. These methods offer more control over error processing and scenario execution.
The provided text delves into the detailed explanations of various error handling directives available in Boost.space Integrator, offering insight into each directive's functionality and implications within the platform's workflow.
Boost.space Integrator returns 429 errors when API rate limits are reached. Strategies include adding a delay with the Sleep module or using the Break error handler to prevent scenario schedule interruptions. Advanced options involve fine-tuning delays based on bundle processing frequencies.