Hi everyone,
running into code by Zapier extended run time error when in testing mode and in zap run mode
sandbox timed out error and support says bug and no ETA avaialble for the fix.Is anyone facing the same error even when configuring extended times out in Python code by more than 30 seconds
some test runs are running for more than 30 seconds even no configuration extended giving inconsistencies in the code by Zapier and with these issues, we cannot deploy to production
+14Hi
Help links for using Code in Zaps: https://zapier.com/apps/code/integrations#help
If you suspect a bug, open a ticket with Zapier Support: https://zapier.com/app/get-help
For us to have more context about the mentioned issued, post screenshots or a Loom.com video.
Hi Troy,
I indeed raised a ticket and wanted to see anyone having the same issue if they add more than 30 seconds and timing out even with extended time.
what’s happening is I build a workflow to read csv and in python, get specific values from system for one column with GET API and update system values plus additional value using PUT.
reference and po amount
not many just 100-150 records and technically it would take 1-2 minutes as system respond for each call in 100 ms and this is working — sometimes working in record with rerun in testing but not when zap is live and upload new csv to the trigger
Support said they will track internally about this bug and closed the ticket and I haven’t received any resolution in two weeks.
I did have one other idea to read csv and pass to webhook as each call but I was expecting this could be easier with extended time as we can build like import file upload
+11Sorry to hear about this
In the meantime, did you have any luck with that other idea you mentioned?
If not, it should be possible to use a Formatter action to read the CSV. That’ll output the row data as a set of line items that you can then pass to a Looping by Zapier action, which would allow the Zap to iterate over the CSV rows and make the relevant API calls for the row within a single Code step. Each loop would need to only make GET and PUT API calls for a specific row, not attempt all of them (so hopefully wouldn’t run into the same errors!). You might want to also think about adding a Delay after queue action to the loop to help space out the requests though, so you don’t run into any rate limits.
Not an ideal solution as this sort of approach would increase your task usage, but hopefully gets things up and running for now. If you give it a try, let us know how it goes!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
