This workflow has not been working last couple of weeks

[dan90]

Your Task History ID

IjU3NjUwNTY4MDYzNzA0MzI1MjY4NTUzYzUxMzE1MTZiNTQzNTBmMzki_pc

Hi there,

This workflow adds data to google sheets.
When it fails (which is does due to read and write quotas) it should run it again.
It used to work fine and was working fine for nearly 6 months.
Now it gets 20 rows in and stops working and hits the read and write quota (used to be a lot more rows than that 60-80 rows).
It also doesn't run the failed steps again even though it is set up to run 2 times if it fails.
It now runs once and never again unless I manually tell it to do it again.
Any reason why this is happening?

So two things:
1) Only about 20 rows get done before it hits read and write quota. Even though when I manually run it I am nearly getting through all my data (60-80 rows).

2) The workflow is only running once and not running the failed steps again as per my settings.

Thanks

 

[Preeti Paryani]

Hello @dan90,

Thanks for sharing the details.

Regarding the workflow re-execution issue, could you please confirm if you've recently changed the auto re-execution settings? Also, if possible, try adding a test to your workflow without making any edits, as this will help us investigate the concern more effectively.

As for the Google Sheets read/write quota, please note that Google enforces quota limits for read and write requests. You can refer to the official documentation for more details.

Usage limits | Google Sheets | Google for Developers

developers.google.com

However, if you're noticing a recent decrease in quota limits or unexpected behavior, we recommend checking the Google support community or reaching out directly to Google Sheets support for clarification. If you receive any updates from them, please do share with us so we can assist you further if needed.

 

[dan90]

IjU3NjUwNTY4MDYzNDA0M2Q1MjY4NTUzMTUxM2I1MTYzNTQzMTBmMzki_pc

Sorry for delay. I am out of the country at the moment.
It has run again on its own but this time getting to row 60 before it stops working. Likely the quota issue which I am aware of hence why I set up the reexecutions. But it looks like the reexecutions are not happening but maybe you can see more information than I can.

It is when it runs automatically it appears to stop short and then not rerun any of the failed steps.
This is new behaviour as it never did this before a few weeks ago or so.

I manually had to do the reexecution again and it went from 60 rows to 86 rows.
Why isn't it reexecuting on its own?

What would you like me to do now?

 

[Preeti Paryani]

Hello,

Thank you for the update, and no worries about the delay.

From what we can observe, the auto re-execution setting typically allows up to three retry attempts. The latest task history dated 7th July appears to have executed successfully.

For the earlier instance you mentioned, it seems a re-execution did occur, but we’re not certain if that was triggered by you or by the system automatically. Since this behavior is relatively new and differs from what you’ve experienced before, we recommend monitoring it closely for now.

If you notice that a task does not get re-executed automatically in future runs, please do share the specific Task History ID with us. This will help us investigate further and escalate the concern to our technical team if needed.

 

[dan90]

Hello,

Thank you for the update, and no worries about the delay.

From what we can observe, the auto re-execution setting typically allows up to three retry attempts. The latest task history dated 7th July appears to have executed successfully.

For the earlier instance you mentioned, it seems a re-execution did occur, but we’re not certain if that was triggered by you or by the system automatically. Since this behavior is relatively new and differs from what you’ve experienced before, we recommend monitoring it closely for now.

If you notice that a task does not get re-executed automatically in future runs, please do share the specific Task History ID with us. This will help us investigate further and escalate the concern to our technical team if needed.

It did not execute successfully on the 7th and I had to manually execute missed rows. As I said it only got to 60 rows of data but there should have been 86.

It should have executed again on the failed "add row" google sheet parts but It didn't.

Thanks

 

[Preeti Paryani]

Thanks for the details. Please allow us sometime to review the issue and we will get back to you with an update as we have some.

 

[Preeti Paryani]

Hello @dan90,

We have escalated this concern to our technical team for further review. Please allow us some time to look into the issue and we will get back to you with the updates as we have some.
Please note that our team may conduct some tests under the workflow to check and verify the issue.

 

[dan90]

Hi there,
Seemed to have worked this week:

IjU3NjUwNTY4MDYzMjA0MzY1MjZlNTUzZDUxMzM1MTYxNTQzNjBmMzMi_pc​

This time It had failed steps but they appeared to have re-executed this time around.
Did tech team do anything to sort it?

 

[Preeti Paryani]

Hello @dan90,

Thank you for sharing the update regarding the issue. Yes, our team has implemented some changes, and it appears that the issue has now been resolved.

Please feel free to reach out if you notice anything further or need any assistance.