Intermittent 429 errors on automation bots sending PDFs (started Aug 27–28, 2025)

[Aplicaciones_Huinoil]

Hi everyone,

We’ve been running AppSheet apps in production for over 5 years where automation bots generate PDF reports and send them by email. Our operators work offline, create 14–27 reports per day, and then sync when they get back online. At that point, all the reports are processed and emailed.

This setup has worked reliably for years with no changes on our side.

Since August 27–28, 2025, we’ve started seeing intermittent failures in the automation monitor. Roughly 4 out of 20 reports fail with this error:

Error encountered in step with name [Send an email]:
Error: Task: ‘Mail Zona PT’ Template Type: ‘Attachment’ could not be read due to
Response status code does not indicate success: 429 (unknown).

What we tried so far:

• Templates are simple (no external images/resources).

• We added a Wait step with random durations between 5 and 15 minutes, so executions don’t run in bursts.

• Audit history confirms that bots are indeed staggered (many are Pending and later Complete at different times).

• Despite this, 429 errors still appear intermittently.

---

Impact:

• Operators’ daily PDF reports are sometimes not delivered.

• This is critical for our operations.

---

Question:
Has anyone else experienced new 429 errors with PDF/email automations since late August 2025?
Could this be related to recent changes in AppSheet rate limits or backend performance?

Any insights, workarounds, or confirmation would be really appreciated.

Thanks in advance!

[JoeBirk]

Yes, having the exact same issue here. Dozens of specifically 429 errors over the last few days. Causing lots of issues for our users.

[Steve]

@Aplicaciones_Huinoil & @JoeBirk, please contact Support for help with this.

[JpChapron]

Im having this issue too !!!

[Rafael_ANEIC-PY]

I just started having the same issue

And I found some of these errors in my bot executions

[JpChapron]

Is anyone investigating this?? Any news from support? I’ve contacted them myself and havent had great support, they couldnt reproduce the issue

[Saddam]

we are having same issue

[Rafael_ANEIC-PY]

I have escalated the issue through appsheet support, I encourage everyone else that is affected by this issue to do the same, we need attention to be given to this problem so that it can be fixed soon. AppSheet Help

[JpChapron]

Great ! Let us know when you have an update

[Rafael_ANEIC-PY]

I’m still experiencing these issues, tagging for visibility @lizlynch @Roderick @alafontant

[JpChapron]

Same Here, most of my operation is compromised and we are starting to look for another solution…

[AppliSuite]

Hi @Aplicaciones_Huinoil ,

Thank you for reporting this critical issue.

We greatly appreciate you taking the time to document this 429 error problem in detail. Your report is invaluable for the community and helps highlight ongoing stability concerns with AppSheet.

Our Similar Experience:

We want to express our support and share that you are not alone in experiencing these issues. While we haven’t seen the massive server outages that plagued AppSheet around April 2025, we’ve been dealing with a persistent pattern of critical errors that significantly impact business operations:

• Sync delays that cause workflows to hang or timeout

• Intermittent 429 errors similar to what you’re experiencing

• Bot execution failures due to synchronization issues

In our case, we’ve had instances where sync delays caused bots to fail mid-execution, resulting in corrupted data that required manual intervention to restore. This is particularly concerning for production environments where data integrity is paramount.

What We Need from the Development Team:

Like you, we’ve implemented various workarounds (staggered execution, wait steps, etc.), but these are band-aid solutions that don’t address the underlying infrastructure problems.

To the AppSheet and Google development teams: We strongly urge you to prioritize a comprehensive, root-cause analysis of these recurring stability issues. The business impact of these intermittent failures is severe, and the pattern of problems suggests systemic issues that require more than incremental fixes.

Our clients depend on AppSheet for mission-critical operations, and the current reliability situation is undermining confidence in the platform. We need sustainable, long-term solutions rather than temporary workarounds.

Community Input Needed:

Has anyone else in the community experienced similar patterns of 429 errors or sync-related bot failures since late August? Let’s consolidate our experiences to help the development team understand the full scope of this issue.

@lizlynch @alafontant @Adam_Stevens @Jana_Mandic @Mike_Procopio

[Saddam]

@AppliSuite ,

thanks for your reporting. I was about to report the same issue. we are experiencing multiple issues with automation.

[Suvrutt_Gurjar]

One of the apps that I am maintaining for a client is also facing these issues of bot not adding the records in another table, even though bot runs in monitor and audit log show the bot ran correctly. Also occasional 429 error is getting displayed.

[Aplicaciones_Huinoil]

We are still experiencing the same issue. Sometimes it happens even when sending only 1 single PDF report at a time.

In addition to the recurring 429 Errors, we are now also seeing new errors like this one:

Error: Data table 'BOMBEO POR MEDIDOR' is not accessible due to: 
The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.

This started to appear alongside the 429s and makes the automations even more unreliable. The problem persists despite implementing delays between executions.

We have already contacted AppSheet Support and our ticket shows that the support team is reviewing our account, but so far we have received no answers or solutions.

Has there been any update on this investigation?

[AppliSuite]

Hi @Aplicaciones_Huinoil ,

While I haven’t experienced this specific issue in my environment, 429 errors in Automation are clearly a critical production incident that severely impacts business operations.

As expected, AppSheet Support provides only template responses that don’t address the root cause. That’s why I mentioned 5 staff members on this thread, but there’s been complete silence from them.

This lack of response to a production-breaking issue is deeply concerning for all of us running live systems on AppSheet.

[Steve]

Yesterday was a holiday in the US.

[HERZ_Aufzüge]

I think a wait condition is the only work arround.. for the moment in my case..
Wait for

A conditionA period of time

Period

Wait until this period of time has passed. The minimum period is 5 minutes and the maximum period is 30 days. Values outside that range will result in an error.

= “000:05:00”

i hope its helpful

[Aplicaciones_Huinoil]

We used a wait with the following formula, in case it helps someone. However, this does not solve the problem and the 429 error continues to occur intermittently. In other words, adding a wait to the automations does not mitigate the issue.

INDEX(
{“000:05:00”,“000:06:00”,“000:07:00”,“000:08:00”,“000:09:00”,“000:10:00”,
“000:11:00”,“000:12:00”,“000:13:00”,“000:14:00”,“000:15:00”},
RANDBETWEEN(1,11)
)

This formula queues the PDF deliveries and sends them randomly within a range of 5–15 minutes, but I repeat, it does not mitigate the 429 error nor the random errors that have been occurring lately

[JpChapron]

I’ve also used wait and still get the issue