Document Database Rate Limits + Make the Builder/AI Respect Them

There is a strict internal rate limit on database operations (mainly write/delete/update), but this limit is not documented. Any action that triggers multiple database updates can easily hit this limit. This makes development unpredictable and forces a trial-and-error approach.

When the limit is reached, the builder shows an error popup that cannot be closed (because the content is too long and the “X” is no longer visible). Clicking “fix with AI” on these specific messages is not a good idea since it leaves it up to the AI to decide HOW to fix it, which can leave to very problematic results. The only way to close this message is leave the app and return just to continue working.

Since the rate limit is unknown, the only workaround is adding random delays and hoping for the best, which wastes time and credits.

The larger issue is that the AI is not aware of these limits. It frequently generates flows that exceed the platform’s internal rate limit, resulting in repeated failures and extra cleanup.

To improve this, please:

1. Publish clear documentation of the database write/delete/update rate limits.

2. Update the documentation whenever the limits change.

3. Make the builder/AI aware of these limits so it avoids generating actions or flows that exceed them.

This would eliminate guesswork, reduce build failures, and create a far smoother development experience.