Issues with the new lazy fetch functionality

upstash / workflow-js

Durable, Reliable and Performant Serverless Functions

MIT License

19 stars 2 forks source link

Issues with the new lazy fetch functionality #29

Open solkimicreb opened 1 day ago

solkimicreb commented 1 day ago

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 commented 14 hours ago

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.