Import Errors

Here are some common import errors and the reasons behind them

When importing your resources into Hava you may get a notification saying that problems were found in your import. These messages come in two different severity levels:

• Warning: these are for your information only and generally mean your import completed successfully.

• Error: these are notifications that something has gone wrong and your import has not completed.

Warnings

Warnings are usually reported when Hava encounters permission errors with a specific region or service related to your import. It means that your credentials don't provide the correct access to import the information, but Hava has skipped over it and continued the import.

To stop the warnings being displayed for your account you can add more permissions to your credentials, or you can safely ignore the warnings.

Resources that do not have sufficient permissions to access and generate a warning will be omitted from your automatically generated diagrams.

Errors

Errors are reported when Hava has encountered a critical problem and had to terminate the import without saving any of the changes. Sometimes this is an issue with your credentials and you'll need to edit them to get your import working.

Sometimes the error relates to a problem communicating with the remote server and your import will be retried.

Some common errors:

Failed to authenticate.

This is the most common error and usually means that the data source credentials you’ve provided are incorrect. Your import will be re-queued to retry, but if it continues to fail the import will terminate.

You can edit your source by clicking ‘Sources’ on the main menu, and then using the ‘cog’ icon to edit your credentials.

Edit credentials for a connected cloud account

There was a remote error and your import is being restarted.

This means there was a network error, a remote server error, or some other problem that means the import couldn’t continue. It will be re-queued and imported again shortly.

Your import has been taking a long time - it's been moved to a dedicated queue.

If you have a very large source with tens of thousands of resources it can spend so long in the queue that it ends up being moved to a dedicated queue. This is so that the import has access to more resources and a longer timeout. This means that your source could potentially take over an hour to import - but it will finish!

If you want to lower the time that your source takes to import you can prevent access to services that you don’t necessarily need imported. For instance, some long AWS imports can be made faster by restricting access to Lambda - especially if you have thousands of functions.

Getting in Touch

If these steps haven't helped you can report issues or concerns to us using the in-app support located in the bottom right of the page, or by sending an email to [e-mail].