The Common Error Message:
"The value has been truncated because it exceeds the 8K cahracter limit for values on the activity page"
"Truncated message", "notice", event.value.notice, event.value.truncatedValue.
What's Happening
When an event payload is very large, Intelligence Hub truncates the displayed payload in certain tools to ensure the UI remains responsive. In these views, the GUI may show a notice about truncation and a shortened representation of the value. This is a display only; it does not change your underlying data or what a pipeline would write to a target.
- Test Reads: Reads greater than 256KB are truncated, and a partial result is returned
- Replay / Activity: Large event payloads may be truncated
- UI behavior: Release notes note a warning when a test read result is truncated
In short, if you see fields like a notice or truncated value alongside event.value in these tools, that's the UI indicating truncation; it does not alter your actual data in any way. Event payloads are still accessed under event.value and event.metadata, not under event.value.tuncatedValue.
Why You Might See event.value With a Truncation Notice
The “truncated message” notice appears when the GUI attempts to preview an event payload exceeding 256 KB. The preview displays a shortened version of oversized values and provides context fields within the event.
- Typical triggers include parameterized reads that return more rows/fields than expected or wide objects (large arrays/strings/blobs).
- If the payload returned by a Test Read exceeds the display threshold, you will view a large event.value in Replay -> Activity, which may be shortened for display.
Example of Truncated Message
