The Issue
A "Wait or Exit" message appears when a dashboard asks the browser to do more work than it can handle at once. This happens when total data received from the DB is too large for the browser.
Possible Root Causes
Multiple factors contribute, such as:
Excessive page objects and type – Too many charts, tables, buttons, and other elements and/or a data intensive chart.
Simultaneous event execution – Multiple data queries firing simultaneously.
Example: A scatter chart attempting to show 10K dots.
Best Practices
Testing throughout development is essential to identify and resolve performance issues before production deployment.
Build incrementally and monitor performance at each stage to identify bottlenecks early
Create versions when new items are introduced allowing you to roll back if you notice performance concerns.
Use developer tools to verify no actions are generating errors that may compound performance issues
Use action logs to track execution flow
Areas to Consider
Variables – Review how variables are created and managed. As an example, where possible, grouping assignments consolidates processing rather than triggering individually.
Loops and Iterative Control Structures – Use action iterative control structures that process data collections sequentially rather than in parallel. This reduces simultaneous processing demands.