If you have questions about the Google Drive integration, check out the Google Drive FAQs:
When does the sync run?
The sync runs when the drive detects a file.
What happens if a file doesn’t sync?
The file remains in the Google Drive folder.
How often should I check the Google Drive folder for unsynced files?
Once every one to two weeks, depending upon volume.
What file types can be synced?
You can sync the following file types:
Note: Google documents won’t sync because it isn’t possible to download them without choosing an export format.
What are the current limitations of the integration?
- Google Drive won’t send notifications informing you which file was added.
- The client path resolution isn’t optimized.
- The client path resolution could be improved to decrease the number of requests and lessen the time it takes to perform its tasks.
What are the entry points for the indexer code?
The indexer is executed from the following:
- Cron jobs (periodic provisioning and auto-clean)
- Web requests (webhook)
- A background worker (actual indexing)
Why won’t a file sync even after reconfiguring the indexer from scratch?
There is a control memory that gets filled for a given file when its indexing begins, so repeated notifications won’t cause duplication on the local database. This memory might not have had a chance to be cleaned due to the nature of the error. This is a common issue during development but should be less common in production.
You have three options:
- Wait until the mark time to live expires (defaults to 30 minutes).
- Wait until the memory is wiped (i.e. Redis is rebooted).
- Remove the syncing marks manually.