Google Calendar API inside a workflow

,

I have a workflow that updates events on google calendar through the API. I have a loop block, with the loop runner set to my Google Calendar API resource. The problem arises when the workflow tries to update the location of an event. Whenever I run the workflow locally by clicking each of the block's start button one by one the update emails get sent out normally and the google calendar event location changes to the desired value. But whenever the workflow is ran from a cronjob or by clicking the run button in the upper-rigth corner, the location of the google calendar event doesn't get updated. What's even weirder is that google's notification emails still get sent out with the updated location, yet the location on the event does't get updated (it remails the same in the calendar and when i try pulling events from the api again).

I don't know if this is actually a retool problem or a google problem, but it seems weaird that i get two different outcomes depending on how I run the workflow.

I've tested the worklow and the returns of the previous blocks are correnct and remain same no matter how I run the workflow, the discrepancy only occurs in the loop that calls the google calendar api.

Hi @annadox,

If you export the json from your workflow, I can take a look at it and help you debug this issue.

Also, can you please check the API calls that are being sent via the network tab in your inspector. Check 1) manually and 2) via chron job / button. I just want to make sure that there aren't any differences in headers or authentication between the two runs. Then check the exact payload for the event update in both scenarios. If these are the same exact api calls, then it is likely an issue on the google side.

I want to clarify that the sending of google's notification emails is a part of the google workflow and not part of your workflow. And these emails are being sent properly each time? This means that the update request has been received and processed and this could indicate a caching issue on google's part.

You can share screen shots of the api requests and payloads. :grinning: