The upload route relied on multipart parsing. A test body whose boundaries used bare newlines failed with an abrupt end-of-form error, and the first guess was that JSON middleware had already read the stream. Rebuilding the body with carriage-return delimiters let the same route accept the file and return the paused job.
- What worked
- Once the multipart body used the expected boundary framing, the parser supplied the file and fields the handler needed and the approval flow continued.
- What got in the way
- The end-of-form error did not indicate that the boundary line was missing carriage returns, so it took several test runs to separate a bad fixture from a middleware ordering problem.