Overview
Solve common problems with Conductor workflows. This guide covers debugging techniques, common errors, performance issues, and integration challenges.Debugging Techniques
Enable Detailed Logging
Trace Execution Flow
Inspect State Changes
Common Errors
1. “Ensemble not found”
Error:Error: Ensemble 'my-workflow' not found
Cause: Ensemble file not in correct location or not deployed
Solution:
2. “Member execution failed”
Error:Error: Member 'fetch-data' failed: Connection timeout
Cause: Network issue, API down, or timeout too short
Solution:
3. “Invalid JSONata expression”
Error:Error: JSONata evaluation failed: Unexpected token
Cause: Syntax error in JSONata expression
Solution:
4. “State property not found”
Error:Error: State property 'userData' not set
Cause: Trying to use state before it’s set
Solution:
5. “AI Provider rate limit”
Error:Error: Rate limit exceeded (429)
Cause: Too many requests to AI provider
Solution:
6. “Database query timeout”
Error:Error: D1 query timeout after 30s
Cause: Slow query or missing index
Solution:
7. “KV value too large”
Error:Error: KV value exceeds 25MB limit
Cause: Trying to store large object in KV
Solution:
8. “HITL timeout”
Error:Error: HITL member 'review' timed out after 1 hour
Cause: Human didn’t respond in time
Solution:
Performance Issues
Slow Execution
Symptom: Workflow takes too long to complete Diagnosis:- Enable Parallel Execution:
- Add Caching:
- Use Faster Models:
High Costs
Symptom: AI bills higher than expected Diagnosis:- Cache AI Responses:
- Reduce Token Usage:
- Use Cheaper Models:
Integration Issues
AI Provider Authentication
Error:Error: Invalid API key
Solution:
Webhook Signature Verification Failed
Error:Error: Invalid webhook signature
Solution:
CORS Issues
Error:Access-Control-Allow-Origin header is missing
Solution:
Testing Issues
Mock Data Not Working
Problem: Mocks not being used in tests Solution:Async Assertion Failures
Problem: Tests fail with timing issues Solution:Deployment Issues
Wrangler Deploy Fails
Error:Error: Failed to publish your Function
Checklist:
Environment Variables Not Set
Error:Error: env.OPENAI_API_KEY is undefined
Solution:
Getting Help
Enable Debug Mode
Collect Diagnostic Info
Check Documentation
Community Support
- GitHub Discussions
- Discord Community
- Stack Overflow (tag: conductor)
Best Practices
- Always add error handling - Use
continue_on_errorand handle failures - Log comprehensively - Structured JSON logs for debugging
- Test locally first - Use
wrangler devbefore deploying - Monitor production - Set up alerts for errors
- Version ensembles - Use Edgit for version control
- Cache aggressively - Reduce costs and improve performance
- Use typed inputs - Validate input schemas
- Document workflows - Add descriptions to ensembles
- Review logs regularly - Catch issues early
- Keep dependencies updated - Security and bug fixes

