Known issues, limits, and debugging

Bots are run asynchronously, meaning they process behind the scenes after you trigger them, and there can be a slight variation in processing time, from instantaneous to a few seconds.
Time-based bots do not always trigger exactly on the hour; the timing can vary anywhere from 0-20 minutes from the designated hour timeframe.
"Email summary" bot actions do not yet support using variables that are allowed in the "Send email" bot action.

There are limits on how many bots you can have per table, and the total volume a bot can fire over a month, defined by your account's usage tier for the tables you own.
There are also limits to how frequent a bot can fire an hour, to avoid abuse and spam. Bots can trigger at most 100 times an hour.
To avoid email spam, a user can trigger at most 100 separate emails to be sent per hour, anything above this will be rate limited to avoid email spamming.
If a bot goes over the limit, it will fail and we will record an error message, but it will not retry the action. The next time the bot is triggered, it will try to run again.

Please be aware: spamming others is a violation and may result in your use of Tables being shut down.

If your bot isn't working like you expect, here are some steps to determine what might be going wrong:

Check that the bot is enabled and set with the correct triggers:

For time-based: if no bot conditions/filters are set, then the bot may trigger for every row.
For column-changed: if the trigger column is deleted/changes type, you'll need to reconfigure the trigger.

Make sure recipients are set correctly, they need to be valid email addresses, or Google accounts (via a Person-type column).
Make sure email subject and body are valid and don't have incorrect use of variables.
You can test that emails are being sent correctly by manually entering your own email address first.

Make sure any values set are correct for the destination column type.
Try "clearing" the value and re-setting the values that are not carrying through or may have been using variables from columns that were deleted or had column type changed.

Make sure the correct script is selected and the correct parameters are passed in the correct order.
Make sure the bot execution history to see if there were any errors or failure messages:
Make sure the Apps Script execution history for errors and debugging messages:
Try other common troubleshooting steps for Apps Script, and reach out to the larger public Apps Script community, which is a great resource for quick questions and answers from other community experts.