Response Limits

Your plan can cap how many survey responses your organization can collect within a period. This limit is actively enforced.

Maximum responses per period

What it controls: the number of new QuestionnaireInstance records accepted within the configured usage period.

• Who it affects: every response channel — field researchers, mobile apps, and public survey links all count toward the same total.
• When it applies: when a response is being submitted.
• What happens when reached: new submissions are blocked with a clear message until the next period begins or the limit is raised. Responses already collected are kept.

Which period is used

The counting window is chosen automatically:

1. Billing/subscription period — if your subscription has a defined current period, responses are counted from the start of that period.
2. Calendar month fallback — if an eligible subscription period start is unavailable or invalid, the resolver uses the start of the current calendar month.

When a new period starts, the count resets and you can collect responses again up to your limit.

Notes

• Re-submitting the same response (an automatic retry that is recognized as a duplicate) does not count twice.
• Existing responses are never deleted when the limit is reached or lowered.

Special values

• The current response guard enforces only a positive MaxResponses value. A missing key, 0, or -1 is treated as uncapped by this guard.
• Catalog-backed plans should use a positive configured quota; the active catalog range is 0 to 250,000.

How to see your usage

• Tenant admins can compare response usage with the effective plan limit in dashboard usage views.

Related Topics

• Understanding Your Plan Limits
• Survey Limits
• What Happens When a Limit Is Reached
• How to Request More Capacity