Testing, Troubleshooting, and Optimization
Testing and Troubleshooting
Test scenarios using Run once to execute with sample data. Execution history shows detailed logs, including bundle inputs/outputs and errors. Debugging involves inspecting module outputs, checking filters, and verifying mappings. Common errors: authentication failures, rate limits, missing required fields, and type mismatches. Optimization reduces operations: use filters to limit bundles, aggregators to batch, and avoid unnecessary modules. Scenario optimization includes setting appropriate cycles, using sequential processing when order matters, and leveraging data stores for caching.
Optimization Techniques
- Minimize operations: Each module run counts as an operation; combine steps where possible.
- Use aggregators to reduce bundle count.
- Schedule efficiently: Avoid overly frequent polling.
- Error handling: Use Break with retries for transient errors to avoid manual intervention.
Traps in Questions
- Execution history retention: Limited by plan; older logs may be unavailable.
- Run once vs. scheduled: Run once ignores schedule and processes current data.
- Operation counting: Every module execution per bundle counts; aggregators reduce operations.
- Filter placement: Filters after a module still consume operations for bundles that pass through the module.
Worked Example / Rule of Thumb
Rule of thumb: "Test with Run once, optimize with filters and aggregators." For example, a scenario processing 1000 records uses an aggregator to combine into one bundle for a single API call, reducing operations from 1000 to 1.