Error Handling for Custom Database Connections

You may receive errors from custom databases. You can also return errors from database action scripts for troubleshooting.

Custom database error types

Database connections may return the following errors:

Error	Action Script	Occurs when…
`new WrongUsernameOrPasswordError(` `<email or user_id>, <message>` `)`	Login	The user’s credentials are invalid. The Log Event Type Codes are: `fu` (invalid username/email) with an empty string for `user_id`, if passed no arguments or a falsey first argument. `fp` (user exists, password invalid) with a `user_id` value of `auth0\|<first_argument>`, if passed a truthy first argument.
`new ValidationError(` `<user_exists>, <message>` `)`	Create	The user already exists in your database.
`callback(<null>,<false>)`	Change Password	The user’s password was not updated.
`callback(<null>)`	Get User	The user is not found.
`new UnauthorizedError(<message>)`	All login scripts	Something went wrong while trying to reach the database. Preferred way of communicating errors back from custom databases to front-end.
`new Error(<message>)`	All login scripts	Something went wrong while trying to reach the database.
`error code: auth0_idp_error;` `user already exists`	Create	Automatic migration to Auth0 is disabled and you attempt to create a user that already exists in your external user store or in Auth0.
`error code: auth0_idp_error;` `user already exists`	Delete	Automatic migration to Auth0 is disabled and you attempt to delete a user with custom database scripts. Error could also manifest as “Error! There was a problem deleting `user@example.com`” or “Sandbox Error: Please implement the Delete script for this database connection”

Return errors

You can return errors from database action scripts using the callback function. For example:

callback(new ValidationError('email-too-long', 'Email is too long.'));

If you use Lock, you can customize the error messages by adding them to the dictionary.

Troubleshoot errors

Test the script using the Try button. If you do not get the expected result or you receive an error, use Actions Real-time Logs, use console.log() statements in your script, and try the connection again. The output of console.log() prints to the Actions Real-time Logs window. You may experience errors using action scripts to import, create, or delete users. Use console.logs to verify the error is a result of using action scripts.

Add Login

Provision Users

Error Handling for Custom Database Connections

Custom database error types

Return errors

Troubleshoot errors

​Custom database error types

​Return errors

​Troubleshoot errors

Custom database error types

Return errors

Troubleshoot errors