Overview
This guide helps you diagnose and resolve common issues with resource collection, configuration, and discovery.Resource Not Discovered
If a resource doesn’t appear after discovery:- Verify the resource exists in the source system
- Check that the Service Account has READ permissions
- Ensure the resource is in a schema/database the connection can access
- Trigger a manual discovery to force a refresh
Collection Failing
If a resource collection fails:- Check the job error message in the Jobs tab
- Verify source system connectivity and permissions
- Review filters - overly restrictive filters may cause issues
- Check for schema changes that broke the collection
Incremental Load Not Working
If incremental loads are collecting more data than expected:- Verify the incremental load field is updating when records change
- Check the field data type is compatible (date/datetime/timestamp)
- Review the last collected timestamp in job details
- Consider using a Full Refresh to reset the incremental cursor
Best Practices
Use Incremental Loads
For large datasets, use incremental loads to improve performance and reduce costs
Set Unique Keys
Always define unique keys to ensure data quality and proper deduplication
Apply Filters Early
Filter data at the source to reduce transfer time and storage costs
Test Schedule Changes
After changing schedules, monitor the first few collections to ensure timing is correct