Troubleshoot Custom Databases

You can use return errors resulting from your custom database connection for troubleshooting purposes. We will also cover some basic troubleshooting steps for your scripts.

There are three different errors you can return from a database connection:

Error	Login Script	Description
`new WrongUsernameOrPasswordError(<email or user_id>, <message>)`	Login	Occurs when the user's credentials are invalid
`new ValidationError(<user_exists>, <message>)`	Create	Occurs when a user already exists in your database
`callback(<null>,<false>)`	Change Password	Occurs when the user's password was not updated
`callback(<null>)`	Get User	Occurs when the user is not found
`new Error(<message>)`	All Login Scripts	Occurs when something went wrong while trying to reach the database

To return an error, call the callback function while passing error as the first parameter:

callback(error);

Was this helpful?/

Example:

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

Was this helpful?/

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

Test the script using the TRY button.

If you do not get the expected result or you receive an error, install the Real-time Webtask Logs extension and use console.log() statements in your script and try the connection again. The output of console.log() will print to the Real-time Webtask Logs window.

Docs

Troubleshoot Custom Databases

Troubleshoot Custom Databases

Types of errors

Return errors

Returning errors when using Lock

Troubleshooting Errors

Was this article helpful?