Skip to main content

Limits

Actual limits can vary by deployment and template complexity, but these practical boundaries help avoid unstable generation.

  • Keep nested structure depth low
  • Avoid very large repeating sections in a single template
  • Keep control/tag naming simple and consistent

Content limits (recommended)​

  • Avoid extremely long text in fields intended for short values
  • Test large repeating datasets incrementally
  • Verify table layout with realistic maximum data

Operational guidance​

  • If generation slows down, split one large template into smaller logical templates
  • Reuse standard field/tag conventions across templates to reduce mapping errors