Error output should include binary data

The idea is:

The dedicated error output of a node should include the incoming binary data.

My use case:

I have a number of workflows that attempt to upload binary files run into either rate limit, or transient, errors. If the error path included the incoming binary files I could easily retry without having to do messy merges and handling looped vs new data in expressions.

Any resources to support this?

Are you willing to work on this?


This has my vote, It makes sense to include it although we never did before so there could be a design reason as to why we didn’t do it.