docs/install/troubleshooting/truncated-logs.mdx
Flow runs have a maximum log size (default 25 MB). When a run gets close to this limit, Activepieces tries to keep it under the cap by truncating large step inputs — you'll see (truncated) in place of the original value.
Truncation applies to step inputs only. Step outputs are never truncated, because downstream steps, subflows, and paused/resumed runs need the original output to continue executing correctly. If outputs were dropped, the next step would receive missing data and fail unpredictably.
The engine works like this:
If the total run data fits within the limit, nothing is truncated.
Otherwise, step input values are replaced with (truncated), starting from the largest, until the run fits.
If the run still exceeds the limit after all inputs are truncated — meaning step outputs alone are over the cap — the run fails with LOG_SIZE_EXCEEDED and an error like:
Flow run data size exceeded the maximum allowed size of 25 MB
If you see this error on a step that downloads or produces a large file (e.g. a multi-megabyte HTTP response, a base64-encoded binary, or a large API payload), the step's output is what's pushing the run over the limit. Since outputs cannot be truncated without breaking subsequent steps, the engine has no choice but to fail the run.
Increase the flow run log size limit by setting the AP_MAX_FLOW_RUN_LOG_SIZE_MB environment variable:
AP_MAX_FLOW_RUN_LOG_SIZE_MB=50