Export Failures
Diagnose and fix export failures with detailed debugging steps.
First Step: Always check export logs first — they contain the specific error message and stack trace.
Export Pipeline
Exports follow a 4-stage pipeline. Failures stop at the failing stage.
Validate config & connect
Get products from Akeneo
Apply transformations
Save to database
Errors by Stage
Initialization Errors
Config validation, credential verification
Missing or malformed config → Check required fields
Invalid Akeneo/DB credentials → Re-test connections
Can't reach Akeneo/DB → Check network/firewall
Recovery: No data fetched or modified. Fix config and retry.
Fetching Errors
Retrieving products from Akeneo API
Rate limit exceeded → Wait 5-10 min and retry
Akeneo API not responding → Check Akeneo status
Filter config error → Check filter syntax
Recovery: Nothing written to DB yet. Safe to retry.
Enrichment Errors
Applying enrichers to transform data
Data type mismatch → Add null checks to enricher
Accessing undefined field → Use field existence condition
Infinite loop in enrichers → Check circular dependencies
Recovery: Nothing written to DB. Test enrichers individually before retry.
Database Write Errors
Saving enriched products to database
Product already exists → Use incremental mode
Insufficient privileges → Grant INSERT/UPDATE
Database slow → Use same-region DB, incremental mode
Recovery: Partial data may exist. Check export count, use incremental to complete.
Quick Error Reference
| Error | Cause | Fix |
|---|---|---|
| 401 | Invalid credentials | Regenerate API credentials |
| 429 | Rate limit | Wait 5-10 min, avoid parallel exports |
| 500 | Akeneo server error | Check status page, retry later |
| E11000 | MongoDB duplicate key | Use incremental mode |
| 42501 | PostgreSQL permission denied | Grant INSERT/UPDATE permissions |
Debugging Steps
Open export details → Expand log viewer → Find last "started" without "completed"
Note error type (MongoError, AkeneoAPIError, EnricherError), code, and message
Re-test Akeneo connection → Re-test database → Test enrichers with sample data
Apply fix → Re-test connections → Create new export → Monitor closely
Recovery Strategies
Partial Export Failure
Some products exported before failure:
- 1. Check exported count in logs
- 2. Don't clear database
- 3. Fix the issue
- 4. Run incremental export
Corrupted Data
Invalid data written to database:
- 1. Note failed export timestamp
- 2. Delete products after that time
- 3. Fix enrichers/config
- 4. Run full export
MongoDB
db.products.deleteMany({
createdAt: { $gte: new Date('2025-01-21T14:30:00Z') }
})PostgreSQL
DELETE FROM products
WHERE created_at >= '2025-01-21 14:30:00';Prevention Tips
- • Export ID
- • Full error message from logs
- • Configuration name
- • Steps that led to failure