Here’s a head scratcher. Anyone able to figure out how I can mitigate this missing data from my servier-side workflow?
Could it be a race condition between the user’s device setting those values and the webhook in the manual workflow kicking off a minute or less later?
Also, I’ve heard good things about ZipZign for pdf generation, esign, and payments.
Yeah, there’s probably a race condition somewhere. I just tested from my phone and it works as intended, but when my client tries from his phone, it doesn’t. Not sure what’s going on.
And thank you for the compliment on ZipZign. It’s been working quite well for my clients. Let me know if you’re interested and I’ll set you up with a discounted plan 
The client-phone detail is the part I would not ignore.
This may not be “JSON missing” as the root problem. It may be that the server-side workflow fires before that user’s device/session has finished committing the values.
One quick split: if the client waits 5-10 seconds after the values appear on their phone before triggering the workflow, do those fields start showing up?
If yes, I would debug sync/commit timing before touching the PDF or webhook step.
From my experience, it could be that the workflow is running before the data has been populated. I always use Wait for Condition to ensure the column contains the expected value before continuing. I ran into this issue many times in the past.
These days, I handle that logic with a JavaScript column instead, it’s much more reliable.
Or, if your app has become this complex, it might be worth moving the entire stock app to your own server. At that point, why build something so complex in Glide?
It was a format date time column that messed things up. That column wasn’t computing fast enough. I had to make sure that the dates and the date time column were correct from the get-go turning respect time zone helped me to do that to fix the issue.
Thanks all!