Usage limits
Flynt meters four kinds of activity per organisation. Your plan decides whether any of them carry a limit; this page explains what is counted, where to see it, and what happens when a limit is reached.
What is metered
| Metric | Counted when |
|---|---|
| Dataset runs | A dataset's SQL is executed against your data source. |
| Dashboard views | A dashboard is opened. |
| Dashboard exports | A dashboard is exported. |
| Card data fetches | A card requests its data. |
Each metric is tracked over two windows: today (the UTC day) and this month (the UTC calendar month). A limit can apply to either window independently -- for example a daily cap and a monthly cap on dashboard views at the same time.
Where to see usage
The Plan & usage page (Admin area) shows a card per metric with the today and this-month counts. Requires the Administrator tier (T7) or above. When a window has a limit, the count is shown against it -- for example "12 / 5,000"; when it has none, you see the count alone.
Limits come from your plan. Most metrics are uncapped on most plans; if you need higher allowances than your plan provides, contact support or see Plans and billing.
What happens at a limit
When a window with a limit is full, further requests of that kind are declined for the rest of the window. Limits are enforced on dataset runs, dashboard views and dashboard exports; card data fetches are metered for visibility.
The person who hits the limit sees a plain message naming the metric, the count against the limit, and how long until they can try again -- for example:
dashboard_view quota reached (5,000 / 5,000 this day). Try again in 32 min.
Nothing is lost: existing dashboards, datasets and cached results are untouched. The action simply waits for the window to roll over.
When limits reset
- Daily windows reset at midnight UTC.
- Monthly windows reset at midnight UTC on the first of the month.
The refusal message always includes the time remaining, so there is no need to work out the boundary yourself.
Good to know
- Usage limits are separate from seat limits. Seats cap how many people can hold a billable tier (Inviting and seats); usage limits cap metered activity regardless of who performs it.
- One dashboard view typically also triggers a data fetch per card on it, so the card-data-fetch count is normally the largest of the four -- that is expected.
- If you set up threshold alerts, an administrator can be notified about activity patterns before users ever see a limit message.