When you make a document generation request, it might fail at the request stage or during document generation.
Request stage errors
While request failures are rare, the following table describes possible error scenarios and how to troubleshoot them.
| Response code | Type | Issue | Solution |
|---|---|---|---|
| 200 | Success | Doc Gen accepted the request for processing. | No action needed. Processing is in progress. |
| 400 | Error | Invalid folder ID, output type, input source, or JSON format. | Verify that you include a valid folder ID, output type, input source, and JSON data format. |
| 401 | Error | Unauthorized request. | Verify that you have access to the file. |
| 403 | Error | Access denied to the content or resource. | Verify that you have access to the file and folder specified in the request. |
| 404 | Error | The template file doesn't exist. | Verify that the specified template file exists. |
| 429 | Error | Too many requests. | See the rate limit guide for information about request limits. |
Document generation stage errors
After Doc Gen validates the request and initiates document generation, failures can occur during processing. To troubleshoot these errors:
- Check the status of the document generation activity.
- View the activity details for the failed request.
- Review the error information and JSON data used in the request.
Box security limitations
If document generation fails due to access restrictions, verify that Box Shield classification policies are configured correctly. Doc Gen requires access to templates to generate documents. If a Box Shield classification policy restricts access to a template, document generation will fail.