Limits

Platform limits and guardrails for metadata and survey version submissions.

Last reviewed

Limits

Use this page when you need the practical limits that shape how submissions, metadata, and survey version rollover behave in production.

These limits are designed to keep response submission reliable. In most cases, extra data is ignored or trimmed rather than causing the main workflow to fail.

Response metadata

  • Up to 25 metadata fields per response
  • Up to 4 KB of sanitized metadata per response
  • If metadata exceeds that budget, extra fields are ignored deterministically
  • The response submission still succeeds

See Response metadata for the recommended metadata patterns and examples.

Survey version submission window

When you publish a newer survey version, the previous version keeps accepting submissions for 12 hours.

That grace window helps with cached clients and older embeds that have not resolved the latest version yet. After 12 hours, older versions stop accepting new submissions and clients should refresh or resolve the latest published version again.