Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Learn more about how to manage errors in the following sections:
You can return custom errors from your application that will be displayed in the file manager.
To do that we reserved codes from 3900 to 3999. An error sent with an error code number in this range displays the message as the error title and the details as the error text.
Your file storage doesn’t support file names with the character “?”
The front end doesn’t stop the upload, as this character is allowed by other APIs and storages
When your API gets the file, returns the following error: Code: 39105 HTTP Status: 400 Message: Upload error Details: The file name is not allowed. Please make sure it does not contain one or more of these characters: \ / < > ? |
The file manager inside the editor displays:
The onWarning callback returns information about a soft error that doesn’t impact the normal usage of the builder. You can use this callback to track these errors, display a message or change any behavior in your application. The callback manages JSON as the output data format.
The onError callback returns information about the application errors. You can use this callback to track these errors, display a message or change any behavior in your application. The callback manages JSON as the output data format.
Code | Message |
---|---|
Code | Message | HTTP Status | Details |
---|
To handle these warnings, add the onWarning callback to :
Code | Message | Detail |
---|
To handle these errors, add the onWarning callback to :
This callback relates specifically to the . The AddOn will transmit the usage data provided by OpenAI with each prompt response, without storing or tracking the data.
To handle these errors, add the onInfo callback to :
1001
Oops! There was an unexpected error. Please try again later.
1100
The template is malformed and cannot be loaded. Check it and try again.
1200
The template cannot be saved.
| FSP Error | 503 Service Unavailable | Default generic FSP Error |
| Something went wrong accessing backend filesystem | 503 Service Unavailable | Default generic Error |
| Resource not found | 404 Not Found | File or directory not found |
| Permission denied | 403 Forbidden | Permission denied to access a file or a directory |
| Resource Already Exists | 409 Conflict | File or directory already exists |
| File Not Uploaded | 422 Unprocessable Entity | Error during file upload |
| Request Error | 400 Bad Request | Server could not understand the request due to invalid syntax |
| User Error | 403 Forbidden | Not a valid S3 custom storage |
| Wrong Username or Password | 401 Unauthorized | Wrong user credentials |
from | Custom error message | Custom HTTP status code |
|
| bee.save is unavailable |
|
| Unknown module name | [Grouping Content tiles]Unknown module name. |
| Duplicate module | [Grouping Content tiles]Duplicate module |
| Invalid modulesGroups configuration | [Grouping Content tiles]Invalid modulesGroups configuration |
| AMP content detected |
| Workspace not available in current plan | The workspace you have configured for the builder is not available for your subscription plan. Message: |
| Action not available when loading template | The action you’re trying to perform on the builder instance is not available during the loading of a template.
Message: |
| Feature not available in current plan | The feature you have configured for the builder is not available for your subscription plan.
Message: |
| Content defaults for the Table module is not valid |
| Generic Bump Error | [Template validation] Default generic bump error |
| Generic Bump Error with warnings | [Template validation] Generic bump error, with warnings. Note: This error is dynamic. Depending on the scenario, you will receive a different error message. Use case: When the Bumper returns 200, but there are some portions of the JSON that should be corrected (for example unrecognized fields). The SDK triggers the |
| Invalid Target Version | [Template validation] The target version does not exists |
| [validation error detail] | [Template validation] The JSON didn’t pass the validation. The cause may be:
Message e.g.: |
| Bump template validation error | page/rows/0/columns/0/modules/0/descriptor/table/rows: malformed field (each row must contain the same number of cells) |
| Missing Template Version | [Template validation] There is no template version in the page |
| Invalid Template Version | [Template validation] There is no template version in the page |
| Transformation Error | [Template validation] Issues during JSON version migration |
| Backward Transformation Error | [Template validation] Issues during JSON version migration |
| Service Error | [Template validation] System failure not related with invalid json files |
The template loaded in the builder contains AMP content, but the builder is not configured with an AMP-compatible workspace. You can react to this warning by loading a workspace, using the .
Message: AMP content has been loaded
Your are not valid for the table module.
As Beefree SDK is improved and updated over time, the JSON structure we use to describe a document may change.
The endpoint bump.getbee.io validates and – when needed – updates a JSON document that had been created with an earlier version of the builder.
This guarantees backward compatibility for older documents: any document (e.g., an email campaign, a template in your email template catalog, etc.) using a JSON structure that the system finds to be out-of-date gets updated automatically the next time it is passed to the builder.
Currently, this feature is working in test mode, tracking any issue with existing JSON documents and allowing us to improve this service. During this testing phase, the system does not stop the loading of the builder when an issue is found.
To read the full list of possible errors, please refer to Template Validation and Update Errors.
The Bump service is the internal codename for our JSON validation/update service. You can read more in our Template Validation and Update article.
1: In case of a Bump error, the JSON parser forwards to the user the error code it receives from the Bump.
1: Additional details are provided, depending on the error that the content worker is reporting.
2: Additional details are provided, depending on the form field that missed validation.
Code | Message | Error | HTTP status | Info |
---|---|---|---|---|
Code | Message | HTTP Status | Details |
---|---|---|---|
Code | Message | HTTP Status | Details |
---|---|---|---|
Code | Message | HTTP Status | Details |
---|---|---|---|
Code | Message | HTTP Status | Details |
---|---|---|---|
Code | Message | HTTP Status | Details |
---|---|---|---|
2000
Generic Bump Error
BAD REQUEST
400
Default generic bump error
2100
Invalid Target Version
BAD REQUEST
400
The target version does not exists
2200
[validation error detail]
BAD REQUEST
400
The JSON didn’t pass the validation.
The cause may be:
Missing keys
Added unknown keys
Message e.g.: required key not provided @ data[u'page'][u'body'][u'content'][u'style'][u'color']
2300
Missing Template Version
BAD REQUEST
400
There is no template version in the page
2400
Invalid Template Version
BAD REQUEST
400
The specified version is unknown
2500
Transformation Error
BAD REQUEST
400
Issues during JSON version migration
2600
Backward Transformation Error
BAD REQUEST
400
Issues during JSON version migration
3000
Service Error
SERVICE FAILURE
503
System failure not related with invalid json files
4001
Authentication error
401 Unauthorized
Authentication header is missing
4005
Authentication error
401 Unauthorized
Bearer token format is invalid
4010
Authentication error
401 Unauthorized
Token expired
4015
Bump service error
400 Bad Request
Error while calling Bump service
...
1
Bump service error
400 Bad Request
…1
4101
JSON pre-processing failed
400 Bad Request
Generic parsing error
4105
JSON pre-processing failed
400 Bad Request
Error while checking special <code> tags
4110
JSON pre-processing failed
400 Bad Request
Error while checking for HTML blocks
4115
JSON pre-processing failed
400 Bad Request
Error while checking conditional statements
4120
JSON pre-processing failed
400 Bad Request
Error while adding conditional statements to rows
4125
JSON pre-processing failed
400 Bad Request
Error while adding styles to rows container
4130
JSON pre-processing failed
400 Bad Request
Error while adding classes for conditional statements
4135
JSON pre-processing failed
400 Bad Request
Error while adding computed styles for each grid block row
4140
JSON pre-processing failed
400 Bad Request
Error while calculating cell widths
4145
JSON pre-processing failed
400 Bad Request
Error while adding background on columns
4190
JSON pre-processing failed
400 Bad Request
Error while adding main CSS styles
4191
JSON pre-processing failed
400 Bad Request
Error while adding main CSS media queries styles
4192
JSON pre-processing failed
400 Bad Request
Error while adding client-specific CSS styles
4501
Pre-processing error
403 Forbidden
Error assembling CSS Rules
4502
Pre-processing error
403 Forbidden
Error compiling general page CSS styles
4503
Pre-processing error
403 Forbidden
Error compiling body CSS styles
4504
Pre-processing error
403 Forbidden
Error converting JSON styles rules to CSS
4201
HTML creation error
400 Bad Request
Generic JSON to HTML conversion error
4202
HTML creation error
400 Bad Request
Communication error to JSON content workers
4210
HTML creation error
400 Bad Request
Communication error with text block worker
4211
HTML creation error
400 Bad Request
Text block worker has notified a processing Error: (…)1
4220
HTML creation error
400 Bad Request
Communication error with button block worker
4221
HTML creation error
400 Bad Request
Button block worker has notified a processing Error: (…)1
4230
HTML creation error
400 Bad Request
Communication error with video block worker
4231
HTML creation error
400 Bad Request
Video/MergeContent block worker has notified a processing Error: (…)1
4240
HTML creation error
400 Bad Request
Communication error with social block worker
4241
HTML creation error
400 Bad Request
Social block worker has notified a processing Error: (…)1
4242
HTML creation error
400 Bad Request
Communication error with icon block worker
4243
HTML creation error
400 Bad Request
Icon block worker has notified a processing Error: (…)1
4244
HTML creation error
400 Bad Request
Communication error with menu block worker
4245
HTML creation error
400 Bad Request
Menu block worker has notified a processing Error: (…)1
4250
HTML creation error
400 Bad Request
Communication error with image block worker
4251
HTML creation error
400 Bad Request
Image block worker has notified a processing Error: (…)1
4260
HTML creation error
400 Bad Request
Communication error with merge content worker
4270
HTML creation error
400 Bad Request
Error handling custom addon module
4601
Rendering error
403 Forbidden
Error cleaning up button module HTML code
4602
Rendering error
403 Forbidden
Error cleaning up text module HTML code
4603
Rendering error
403 Forbidden
Error checking form elements
4604
Form validation error
403 Forbidden
Error in (…)2
4605
Rendering error
403 Forbidden
Custom video format not supported
4920
Rendering error
403 Forbidden
Video block is corrupted
4600
Rendering error
403 Forbidden
(…)1
4301
HTML post-processing error
400 Bad Request
Generic post-processing error
4310
HTML post-processing error
400 Bad Request
Error while transforming images URI
4320
HTML post-processing error
400 Bad Request
Error inserting custom HTML codes
4330
HTML post-processing error
400 Bad Request
Error replacing custom Beefree SDK code tags
4340
HTML post-processing error
400 Bad Request
Error inserting display conditions
4700
Post-processing error
403 Forbidden
Error assembling the final HTML page