Google Drive Ingestion Permissions

Some Google Drive files fail to ingest into memories and immediately move to an Error state. This usually happens when the file owner has only shared the document with you as a Viewer.

What You Will See

• The file stays in the Error state inside Google Drive Memory after you trigger ingestion.

• Retrying ingestion without changing permissions does not help.

Why It Happens

Google Drive restricts which collaborators can access a file’s revision history. If you are shared on a document with Viewer permissions, Google will not expose the revision history - even if you’ve granted the Hana access to your Google Drive files.

Hana utilises the file’s revision history for syncing, so you will need to update your role (to Editor or Owner) before ingestion can succeed. If you only have Viewer access, the ingestion job cannot proceed and will move to an Error state because revisions are hidden from your account

To proceed, you’ll need to request Editor or Owner access from the file’s owner.

How to Fix It

1. Ask the file owner or admin to change your sharing role to at least Editor role (or give you ownership).

2. After the role is updated, retry the ingestion.

3. Confirm that the file now appears with a Success status.

Need Help?

Email hana-bot@hanabitech.com if the issue continues after updating the sharing role. Include the file link so we can investigate quickly.