Troubleshooting
This document covers common OpenETL issues, debugging procedures, and support resources.
Common Issues
Module Not Found Errors
Symptom: Import errors for openetl or adapter modules
Resolution:
- Verify installation:
npm list openetl - Reinstall dependencies:
npm install - Check package.json for correct package versions
Silent Pipeline Failures
Symptom: Pipeline completes without errors but no data is processed
Resolution:
- Verify Vault credentials (
client_id,client_secret,refresh_token) - Enable logging to capture error events
- Test adapter connection independently
- Verify endpoint configuration in connectors
Rate Limit Errors
Symptom: HTTP 429 errors or throttling messages
Resolution:
- Configure
rate_limitingin pipeline (see Rate Limiting) - Reduce
requests_per_secondandconcurrent_requests - Increase
max_retries_on_rate_limit
Debugging Procedures
Enable Event Logging
orchestrator.runPipeline({
id: 'debug-pipeline',
source: { /* ... */ },
logging: event => {
console.log(`[${event.type}]`, event.message || event);
},
});
Test Adapter Connections
Isolate connection issues by testing the connect() method:
const adapter = adapterFunction(connector, credentials);
await adapter.connect(); // Test authentication
Isolate Components
Test pipeline components independently:
- Test source adapter extraction only (use
onloadcallback) - Test target adapter loading with static data
- Test transformations with sample data
Support Resources
Documentation
- Architecture Overview: Framework design and components
- Error Handling: Error management and retry configuration
- Adapters: Adapter interface and implementation
Community Support
- GitHub Issues: https://github.com/jspreadsheet/openetl/issues
- Issue Reporting: Include error messages, pipeline configuration, and reproduction steps
- Feature Requests: Submit via GitHub Issues with use case description