Troubleshooting
On this page
When collecting and processing data in Adverity, you might encounter various issues that need investigation. Find the symptom you see, then follow the link to the guide that helps you identify, analyze, and resolve it.
Troubleshooting by symptom
- A fetch failed
For common fetch errors, such as No space left on device, or a fetch status that stays Collected, see Troubleshooting errors when collecting and loading data. To see the issues of a datastream, see Viewing datastream issues. If the error is specific to a data source, see Troubleshooting for specific data sources.
- The data does not match the source
See Troubleshooting data discrepancies to find out what a data discrepancy is and how to identify it.
- A load to a destination failed
See Troubleshooting errors when collecting and loading data, for example for load errors involving key columns.
- An authorization expired or is invalid
Update the authorization, as described in Managing authorizations. For authorizations to a specific data source, see Authorizing specific data sources.
- A dbt run failed
See dbt troubleshooting for common issues with dbt project configuration and execution.
- Data quality issues appear
See Viewing details of the Data Quality issues for the details you get for each type of monitor.
Troubleshooting for specific data sources
These data sources have a separate troubleshooting page:
These setup guides have a Troubleshooting section:
For any other data source, open its setup guide from the data sources directory.
Troubleshooting for specific destinations
For load errors that apply to every destination, see Troubleshooting errors when collecting and loading data. These destination guides have a Troubleshooting section:
Ask Connect Agent
Instead of looking up an error yourself, you can ask Connect Agent why a fetch failed. It checks the fetch history and the error, explains what went wrong, and suggests a fix.