Translation Content API: Errors

This table outlines errors that might be issued when calling the Translation Content API. The list includes error codes, and troubleshooting guidance to help you resolve these issues.

HTTP STATUS
ERROR NAME
RULE NAME
DESCRIPTION & TROUBLESHOOTING
BAD_REQUEST (400)WixValidationRuntimeExceptionContentSizeValidationRuleThe content size exceeds 1MB (1,048,576 bytes). Reduce its size by removing unnecessary data.
BAD_REQUEST (400)WixValidationRuntimeExceptionSchemaFieldsExistValidationRuleField ID not found in the schema. Ensure all content fields match the schema. Remove or rename unmatched fields, or update the schema to include them.
BAD_REQUEST (400)WixValidationRuntimeExceptionFieldTypeValidationRuleField type doesn't match the schema. Update the content field type to align with the schema.
BAD_REQUEST (400)WixValidationRuntimeExceptionRepeaterIdSpecifiedValidationRuleInvalid repeater field ID. Ensure repeater field IDs are correctly specified and follow the required format.
BAD_REQUEST (400)WixValidationRuntimeExceptionMaxLengthValidationRuleText exceeds the maximum length. Shorten the text to fit within the specified limit.
BAD_REQUEST (400)WixValidationRuntimeExceptionMinLengthValidationRuleText is shorter than the minimum length. Extend or pad the text to meet the required length.
BAD_REQUEST (400)WixValidationRuntimeExceptionFieldFormatValidationRuleInvalid field value format. Update the field value to match the required format.
BAD_REQUEST (400)WixValidationRuntimeExceptionSchemaExistsValidationRuleSchema not found. Ensure the schema ID is correct and valid.
BAD_REQUEST (400)InvalidArgumentExceptionMissing revision value when calling the Update method. Specify a value for the revision property when updating the entity.
NOT_FOUND (404)EntityNotFoundContent not found. Verify that the ID used in the Get Content method exists in the system.

General Troubleshooting

If you encounter any of these errors:

  1. Check your content against the schema definition.
  2. Ensure all required fields are present and correctly formatted.
  3. Verify that field values meet the constraints specified in the schema such as length, format, or type.
  4. If the error persists, contact support with the specific error message and details of your operation.
Did this help?