Issues with the new lazy fetch functionality

[solkimicreb]

Hey! Since I updated to v0.2.0. I started getting these two errors:

• Cannot destructure property 'meta' of 'ctx.requestPayload' as it is undefined. from the failureFunction.
• Upstash Qstash: Failed while decoding base64 "undefined". Decoding with atob and returning it instead. InvalidCharacterError: The string to be decoded is not correctly encoded. from the main workflow.

I suspect these are related to the new lazy fetch functionality and the body being undefined.

[CahidArda]

Hi there,

It looks like this can happen if the workflow is triggered with an empty payload. But since you check ctx.requestPayload.meta, I assume you don't call the workflow with empty payloads.

Did you observe these errors in workflows which were started before the version upgrade or do they still happen consistently after the version upgrade?

Either way these errors shouldn't have happened, we will look into addressing them.

[solkimicreb]

I am pretty sure they were started after the version upgrade but that's a good point. I will try to repro with the upgraded version and a clean instance when I have some time.

Edit: yep, the workflows were called with large payloads.

[solkimicreb]

Hey!

The issue still persist with the latest version. I found this (probably newish) documentation about my issue: https://upstash.com/docs/workflow/troubleshooting/general#context-call-execution.

• It only happens with 2.0 + versions for me (with the new lazy fetch large payload functionality)
• I still can't upgrade to 2.0 + even with the proposed fix from the docs as ctx.requestPayload is also undefined in the failureFunction where I am not sure how to work around the issue.

[CahidArda]

Hi @solkimicreb,

Is there any chance you can provide a reproduction code sample?