I’m using a non-profit workspace account for the first time and hit a rate limit quota. I believe it is on AppSheet Core license. I can’t find where the limits are for sending emails through bot automations. This hasn’t happened on my enterprise plus before.
In your original post the error mesage seems to be cut off. There was an “OR” postion and maybe that is the problem - not the quota. For 134 emails, I seriously doubt it was quota related.
I seem to recall, that the email generation would stop if there was an email address with incorrect syntax encountered.
I left it off the screenshot because it included PII of our user’s email addresses. You are correct that it does state:
“Warning: Email failed to be sent. This is due to hitting a rate-limit quota or invalid recipients”
I did check to see if the syntax was valid on the emails. What is interesting is that after the 30~ish minutes I was able to resend all the remaining emails without issue and without having to manipulate or remove any of the emails. This leads me to believe that it was rate-limit instead of the recipients being the cause.
I’m curious why the warning combines the two issues into one “warning”. It would be easier to diagnose if it was one or the other.
For diagnostic purposes:
The user creates an “event” record that on form save triggers a grouped action (2 Total).
The first action in the group executes an action on a set of rows (a slice called deliveries). This referenced action adds a new row to another table called “communication”. A bot is watching for adds to the communication table and sends the email (the one that got rate limited).
The second action in the group executes an action on a set of rows (a table called applicant) and it changes an enum value. There are no automations triggered by this action.
There is an expected lag as the 268 actions are calculated and the total sync time lasted several minutes. It did not appear that there were any challenges. After everything synced all the rows in the communication table were added as expected and all the enum values were changed in the applicant table as expected.
Thanks for feedback and help! I hope this post helps someone in the future. I’ll have an opportunity to push the event in a few days to see if it causes the same issue again. If it does, I’ll report back and identify attempts at a work around.
If I’m missing something such as a variable in the situation to help diagnose, please feel free to call it out. Thanks Steve and Willow!
Thank you this valuable discussion. I did work with the AppSheet engineering team to add email recipient limits to the documentation. See email recipients.
Glad to see I wasn’t the only one with this issue. It flew under the radar for a few days because it also didn’t throw any errors in the Automation Monitoring Overview.
In our case the Bot was just fired twice a day and had about 7 to 12 recipients each time. Weirdly enough that amount already triggered the limit.
Also: It was seemingly random which mails went through and which ones didn’t. Sometimes it worked, sometimes it didn’t.
I ultimately had it resolved with the AppSheet Support, but they couldnt solve it on the spot. What was frustraing was that this “error message” wasn’t on any documentation or Community thread.
And I’d suggest that something like this should definitely throw an error in the Automation Monitoring page. We skimmed through it earlier and thought everything was fine seeing all the green “Completes”.
Unfortunately it happened to me again today. The documentation now says 200-400 address per hour for a CORE license, but I hit the same hard stop at 94 emails again today.
I’m was thinking that it might be a per minute issue, but If I calculate my email per minute its roughly 4.48 emails per minute and the 200-400 per hour calculates out to 3.33 to 6.67 emails per minute. I feel like I should be within the threshold.
Is it possible to get more clarity on this issue? At least get the monitor to show a failed status instead of a complete status?
