Troubleshooting Errors
Every Nected operation requires that certain prerequisites are met for that task to be successful. If the condition is not met, then you might receive an error that indicates that the operation cannot be performed.
The following table lists the most common Nected operation error codes and messages:
Table 4 – Error Codes and Messages
| Internal Server Error |
| Bad Request Body |
| Bad Request Body |
| Request Params are not correct |
| route Not Found |
| invalid JSON provided |
| unauthorized access |
| Daily limits crossed for invocations |
Errors You May Encounter in Database Integration
When integrating a database with Nected, it's important to be aware of potential errors that may occur during the process. Regardless of whether you are working with PostgreSQL, MySQL, MongoDB, or Redshift, these databases operate at the TCP layer, and many of the issues you might encounter relate to connectivity and access.
Here are some common errors you may face and how to address them:
IP Blacklisting:
What to Expect: If you experience difficulty connecting your database to Nected, it could be due to IP blacklisting. IP blacklisting is a security measure used by some databases to restrict access from specific IP addresses.
How to Resolve:
To address this issue, you should whitelist Nected's IP address, which is "43.205.43.45". Whitelisting ensures that Nected's requests are allowed by your database's security measures. It's crucial to configure your database's access controls to permit incoming connections from this IP.
Database Non-Existence:
What to Expect: If you attempt to connect a database that does not exist, Nected will encounter an issue during the connection process. The database must be available and correctly configured.
How to Resolve:
Ensure that the database you are trying to connect to exists and is operational. This includes verifying that the database server is up and running and that the database instance or schema you want to access is properly set up.
Insufficient Database Authorization:
What to Expect: To work with a database, you must have the necessary authorization to access the database and its tables. If your database authorization is insufficient or you lack access to specific tables, issues may arise during database operations.
How to Resolve:
To address this issue, you need to ensure that you have the appropriate access rights to the database and the specific tables you intend to work with. Contact your database administrator or access control administrator to configure the necessary permissions.
HTTP 404 Error:
Important Note: Nected may show a 404 error if you attempt to connect to a database that does not exist or if you lack access rights to the database.
What to Expect: A 404 error typically indicates that the resource you are trying to access could not be found. In the context of database integration, this usually points to either the database's non-existence or insufficient access rights.
How to Resolve:
To resolve a 404 error in this context, focus on ensuring that the database exists and that you have the required access rights. This may involve collaborating with your database administrator or relevant personnel to address the underlying issues.
Database Schema Visibility in Data Set Creation
When creating a data set within Nected, users have the convenience of viewing the database schema on the right side of the editor tab. This feature allows users to access and utilize information from the connected database during the data set creation process.
However, if you find that the schema tab is not displaying the expected information, it may be due to the absence of a database at the specified path. In such cases, the schema information cannot be retrieved because there is no database to connect to.
To address this issue:
Access the Database: Ensure that the database you intend to connect to exists and is accessible. Verify that the database server is running and properly configured.
Nected relies on the presence of a functional database at the specified path to display the schema information. If the database does not exist or is not accessible, there is little that can be done from Nected's end to resolve the issue. Therefore, it is crucial to confirm the database's availability and connectivity to successfully utilize the schema information during data set creation.
It's important to note that the success of your database integration largely depends on the availability and access rights of the database itself. While Nected provides tools and features for integrating with databases, issues related to the database's existence and authorization are typically beyond Nected's control. By addressing these common issues proactively, you can ensure a smoother and more successful database integration process.
Facing Error While Creating or Editing a Dataset:
Limitation on Write Queries: However, while Nected supports both read and write operations in general, it is important to note that in the case of datasets, it only supports read-only operations.This limitation means that users can't add new databases or create and edit datasets in a traditional SQL sense.
Nected integrates with databases like MongoDB, PostgreSQL, and MySQL, but it's important to note that some queries allowed in direct database access may not work the same way in Nected, and might not always trigger errors. For details on supported and non-supported queries for each database in Nected, refer to our documentation here.
While Writing Queries for Rule Actions:
Dataset Visibility: If the user cannot see their dataset table when writing SQL codes for rule actions, they should click the refresh button at the top right corner of the Schema section. This can help update the dataset list and make it visible.
Write Queries: In Nected, while rule actions do allow for write queries, it's important to note that even when operating in the "Staging" environment, if a test is run and an action is successfully executed, the effects of this action will be visible in the original database. This means that despite being in a testing phase, the outcomes of actions performed in "Staging" can directly impact the live database. Therefore, users should exercise caution even when testing in the "Staging" environment, as these actions are not merely simulations but can result in actual changes to the database. It's always advisable to thoroughly review and understand the implications of any actions before executing them, even in a testing environment.
When it comes to writing actions in Nected, Nected allows user to perform various actions on their data, such as inserting, updating, and merging records, all while ensuring data integrity. However there are also some limitations on the types of queries and operations that can be performed to ensure data consistency and security. For details on supported and non-supported queries for each database in Nected, refer to our documentation here.
Understanding these common troubleshooting steps and limitations can help users effectively work with datasets and rule actions in Nected while managing and interacting with MySQL databases. It's important to be aware of the read-only nature of datasets in Nected and to take proper precautions when transitioning from the "Staging" to "Production" environment to prevent unintended changes in the actual database.
Errors You May Encounter with API calls in rule action:
When working with API calls in your rule actions, it's important to be aware of potential errors that may arise during the process. While API calls are primarily HTTP-based, the main categories of errors you might encounter are HTTP status codes, particularly those in the 500 series. However, it's essential to note that Nected does not display the 404 error ("{"error":"Endpoint not found"}") even during API integration.
Here are some common errors you may face and how to address them:
HTTP 500 Series Errors:
What to Expect: These errors indicate that the server has encountered an issue while processing the API request. They can be caused by various factors, such as server misconfigurations or issues on the API provider's end.
How to Resolve:
Check API Endpoint: Ensure that the API endpoint you are calling is correct and accessible.
Verify Request Data: Double-check the data you are sending in your API request. Ensure it adheres to the API provider's requirements.
Contact API Provider: If the issue persists, reach out to the API provider's support for assistance or information on the specific error.
HTTP 404 Error:
Important Note: Nected does not display this error in the API integration stage, but it is essential to be aware of it.
What to Expect: The 404 error typically indicates that the API endpoint could not be found. If you encounter this error, it's likely a result of an issue on your end.
How to Resolve:
Check API Endpoint: Verify that the API endpoint is accurate and exists.
Review Configuration: Review your rule action's configuration to ensure you are calling the correct endpoint and passing the necessary data.
Monitor Output: After including the API as a rule action, make it a habit to monitor the JSON output in the action tab. This will help you identify any 404 errors.
HTTP 403 Error:
What to Expect: An HTTP 403 error signifies that your request has been denied access. This can occur due to various reasons, such as inadequate permissions or IP blocking.
How to Resolve:
Whitelist Nected's IP: If you receive a 403 error, it may be necessary to whitelist Nected's IP address, which is "43.205.43.45". This ensures that Nected can access and interact with the API without any access restrictions.
It's essential to understand that while Nected provides tools for integrating APIs and configuring rule actions, certain errors may be outside of Nected's control, particularly those related to the API provider's infrastructure or your rule action's setup. Regularly monitoring the JSON output and staying vigilant about your API calls will help you quickly identify and address any potential issues. If problems persist, don't hesitate to reach out to the API provider's support for assistance and guidance.
Last updated
