Hello Adalo family!
Has anyone successfully steered through the constant 503 and 429 Integromat errors that pop up seemingly randomly?
Thanks!
Hi Thomas,
To be honest I rarely use Integromat so I would just submit a support ticket for this.
Hi @anon28807528,
I’ve seen this as well.
429 usually means “Too many requests” - are you trying to get a large amount of data in a short period?
As for 503, I suspect that it might be caused by Adalo servers “overload”.
Anyway, as @James_App_Maker suggested, it’s better to submit a ticket so that Adalo team can have a look.
Best regards, Victor.
I’ve gotten over 12 503 errors today alone, causing all of my Integromat scenarios to fail and stop.
Has anyone else seen an uptick?
I know this is an old thread, but I’m getting daily 503 errors from Integromat polling Adalo collections.
Last week I was getting so many errors I had to halt the scenarios for a while.
Just in case anyone from Adalo is watching this thread…
I still get them here and there, especially with doing large-number scenarios. My main workaround is to make sure error handling is setup. Are you doing that at least?
I actually don’t have error handling setup for this scenario. Luckily it only looks for changes (which don’t occur often in this case) so I didn’t think about the retry error handling. Thank you for the tip!
Edit: in this case, I think I just need an “ignore” handler, because it will just retry at the next interval and no data would be missed/lost. Hopefully that will stop me getting the error emails… But I may miss if Adalo API is down again…
1 Like