- Starter
- Business
- Enterprise
- On-Premise
- Add-on
Overview
When event-driven Flows receive data, Etlworks can store incoming payloads (messages) in their original format.
This allows you to:
- Inspect incoming data
- Troubleshoot issues
- Replay or audit requests
Enable message storage
Message storage is disabled by default.
To enable it:
- Open the schedule for the event-driven Flow
- Enable Keep Messages
When enabled, all incoming payloads are stored in the database.
Messages
A message is the raw payload received by Etlworks from an external system.
Examples:
- JSON request
- XML payload
- Form data
- API request body
View messages
Messages can be accessed in the Messages window.
The grid displays:
- Message timestamp
- Processing status
- Associated Flow execution
View message content
To view the raw payload:
- Open the Messages window
- Click the message icon
This displays the message exactly as received.
View processing status
To see how a message was processed:
Click the Status link. This opens the Flow execution details for that message.
You can:
- Check execution result
- View logs and errors
- Analyze processing behavior
Typical use cases
- Debugging malformed payloads
- Verifying data received from external systems
- Auditing inbound requests
- Replaying scenarios during testing
Notes
- Messages are stored in the database
- Storage may increase database size over time
- Enable only when needed for debugging or auditing
Summary
- Inbound messages can be stored and inspected
- Each message is linked to a Flow execution
- Useful for debugging, validation, and auditing