This article explains why errors may occur when uploading a custom form using a JavaScript Object Notation (JSON) bundle in Auth0. The following errors may be observed:

• A generic exception is displayed in the Auth0 Dashboard (Graphical User Interface)

• A 404 Not Found error is returned when using the Auth0 Deploy Command Line Interface (CLI) or the Management API

• Auth0

• Custom Forms (JSON Bundles)

• Auth0 Dashboard (GUI)

• Auth0 Deploy CLI

• Management API

The 404 error or generic exception is caused by a JSON bundle structure that does not comply with the required Auth0 format.

The backend validation expects a specific schema for form definitions. If the provided JSON is malformed, missing required fields, or contains invalid entries, the API endpoint may return a 404 error, or the GUI will throw a generic exception. This can occur if the JSON file was created manually without adhering to the correct structure.

Ensure the JSON bundle's format is valid. There are several methods to resolve this:

1. Validate the JSON Structure: The most reliable method is to base the file on an official template. Compare the custom JSON against these templates to find and correct discrepancies. Valid form templates can be downloaded from the Auth0 Developer Resources.

2. Use an Exported Form: If possible, configure a form in the Auth0 Dashboard and export it. The exported JSON is guaranteed to be in the correct format and can be used as a reliable base for modifications or for importing into other tenants.

3. Update the Auth0 Deploy CLI: If you are using the Auth0 Deploy CLI, ensure that the latest version is running. Older versions may not support this feature correctly, which can also result in errors.