What Causes Importing Issues?
Sometimes you might see error messages when importing data from a different system. In this article, we'll try to pinpoint the possible import problems.
Error code 401
If you see the error code 401, your credentials are either incorrect or expired. Make sure to provide the correct credentials when connecting your system to Plecto. That includes your username, password, API key, or others. Follow our integration guides to see what credentials to provide for each of the systems.
If your credentials are expired, go to Data management > Credentials to refresh your credentials. After that, go to the data source settings and run a manual data import. Learn more in Manual Refresh and Import of Data.
Error code 403
Error code 403 means that you don't have access to this data type or your system's API is not enabled. In some cases, employees can only access part of the external system. Therefore, make sure you have admin access to your system or ask other admins to integrate your system to Plecto.
Error code 404
If you see the error code 404, it could be either because the integration is configured incorrectly or your provided subdomain is incorrect. Please contact us if you suspect an issue within our integration.
Subdomain is the first part of a website's full domain. For example, in the URL
help is the subdomain.
Error code 429
Error code 429 indicates rate limits, which means that you have exceeded the maximum number of allowed requests per minute/hour – you're trying to import too much data at once. If you're sending data to Plecto through a custom API, you can find the limits in this article: API Limits. Otherwise, rate limits depend on the system you integrate. Try to find out if you can increase the limits on your system's side.
If you see 5xx error messages, it means that the issue is caused by the external API (your system). In that case, there's nothing we can do – we'll have to wait until the developers address the issue. :)
Progress bar loading slowly
If you run a manual data import and select a large time period, the data import can take a while to finish. Longer time periods that possibly contain a lot of registrations can lead to unexpected errors or long data imports.
Was this article helpful?
Please leave a comment to help us improve.