If you're seeing MINIMUM_VALUE_REQUIRED or MAXIMUM_VALUE_REQUIRED errors in your Flow JSON, it means you've set a property value that falls outside the allowed range. The fix is simple: set values within the documented limits for each component.

For example, in a PhotoPicker, the min-uploaded-photos must be between 0 and 30. If you set it to -1 or 40, the validator will throw these errors:

{
  "type": "PhotoPicker",
  "name": "ID_Proof",
  "min-uploaded-photos": -1,
  "max-uploaded-photos": 40
}

Why This Happens?

Some attributes are required to stay within a defined minimum and maximum range—and this range is enforced strictly. In the case above:

  • min-uploaded-photos: -1 → too low (minimum is 0)

  • max-uploaded-photos: 40 → too high (maximum is 30)

These constraints ensure that the user experience is safe and predictable. Meta defines these limits based on what the WhatsApp client can reliably support.

How to Fix It?

Always refer to the official flow schema or documentation for valid ranges. For PhotoPicker, update your code like this:

{
  "type": "PhotoPicker",
  "name": "ID_Proof",
  "min-uploaded-photos": 1,
  "max-uploaded-photos": 5
}

This keeps both values within the [0, 30] boundary.

Pro Tip

If you're dynamically generating Flow JSON, add a validation layer to check these ranges before deployment. It'll save you from unnecessary debug cycles and publishing failures.

For more troubleshooting insights related to WhatsApp Business API, check out heltar.com/blogs.