onyx-dot-app/documentation
1
0
Fork 0
mirror of https://github.com/onyx-dot-app/documentation.git synced 2026-07-25 05:35:37 -04:00
Code Issues 17 Packages Projects Releases Wiki Activity

Explain relationship between Error "Stopped mid run, likely due to the background process being killed" and OAuth expiring #2

New Issue
Open
opened 2026-02-15 17:05:32 -05:00 by yindo · 1 comment
yindo commented 2026-02-15 17:05:32 -05:00
Owner
Copy Link
Copy Source

Originally created by @theship on GitHub (May 10, 2024).

Add docs on re-authenticating with GDrive OAuth

Setting up Google Drive OAuth is tricky, and the docs do a good job of walking through it. But there is no indication that the OAuth creds expire in 7 days, at which time you must pause and delete all connections, and revoke access in order to trigger re-auth.

Maybe some details after the Indexing section would be useful. May I suggest something like the attached new section at the bottom of the Google Drive OAuth page? Or maybe this sort of thing should go in some Errors or Troubleshooting section.

Suggested new content

Revalidating your OAuth credentials with Danswer

In test mode, your OAuth credentials expire after seven (7) days. This means you must revalidate your Google Drive credentials with Danswer every week. To trigger token refresh and reset, go through the OAuth consent screen again.

What to look for

If you see the following error message in a connector log (for example: http://localhost:3000/admin/connector/<connector_id>), it may be that your Google Drive credentials have expired.

Stopped mid run, likely due to the background process being killed

Docker or Kubernetes logs may give some indication that your OAuth credentials have expired. For example, if you run the following docker command:

docker exec -it danswer-stack-background-1 cat /var/log/update.log | grep -v 'new indexing tasks\|current UTC time'

You may see the following error message:

PermissionError: Unable to access Google Drive - unknown credential structure.

What steps to take

When AUTH_TYPE=disabled, "Revoke Access" only works after deleting all of the Google Drive connectors along with their indexed files. This means that you must pause and delete any Google Drive connectors. After you reauthenticate, you can add connectors back to start indexing again.

To re-authenticate with Google Drive, follow these steps:

  1. Navigate to the Admin Dashboard and select each Google Drive Connector (for example: http://localhost:3000/admin/connector/<connector_id>).
    • Pause the connector if it is running.
    • Select the "Schedule for Deletion" button.
      When the connector is deleted, you see an error that the connection can't be found. At this point, the indexed files are also deleted. This is why you must reindex the files after re-authentication.
    • Repeat this pause|delete step for each connector.
  2. Go back to the Google Drive Connector page (for example: http://localhost:3000/admin/connectors/google-drive) and click on Revoke Access to remove the stale OAuth credentials.
  3. When the button changes to Authenticate with Google Drive, click on it to step through the OAuth flow again.
  4. Add connectors back to start indexing again.
Originally created by @theship on GitHub (May 10, 2024). # Add docs on re-authenticating with GDrive OAuth Setting up Google Drive OAuth is tricky, and the [docs](https://docs.danswer.dev/connectors/google_drive/oauth) do a good job of walking through it. But there is no indication that the OAuth creds expire in 7 days, at which time you must pause and delete all connections, and revoke access in order to trigger re-auth. Maybe some details after the [Indexing section](https://docs.danswer.dev/connectors/google_drive/oauth#indexing) would be useful. May I suggest something like the attached new section at the bottom of the [Google Drive OAuth page](https://docs.danswer.dev/connectors/google_drive/oauth)? Or maybe this sort of thing should go in some Errors or Troubleshooting section. ## Suggested new content ### Revalidating your OAuth credentials with Danswer In test mode, your OAuth credentials expire after seven (7) days. This means you must revalidate your Google Drive credentials with Danswer every week. To trigger token refresh and reset, go through the OAuth consent screen again. #### What to look for If you see the following error message in a connector log (for example: http://localhost:3000/admin/connector/<connector_id>), it may be that your Google Drive credentials have expired. Stopped mid run, likely due to the background process being killed Docker or Kubernetes logs may give some indication that your OAuth credentials have expired. For example, if you run the following docker command: ```bash docker exec -it danswer-stack-background-1 cat /var/log/update.log | grep -v 'new indexing tasks\|current UTC time' ``` You may see the following error message: PermissionError: Unable to access Google Drive - unknown credential structure. #### What steps to take When `AUTH_TYPE=disabled`, "Revoke Access" only works after deleting all of the Google Drive connectors along with their indexed files. This means that you must pause and delete any Google Drive connectors. After you reauthenticate, you can add connectors back to start indexing again. To re-authenticate with Google Drive, follow these steps: 1. Navigate to the Admin Dashboard and select **each Google Drive Connector** (for example: http://localhost:3000/admin/connector/<connector_id>). - Pause the connector if it is running. - Select the "Schedule for Deletion" button. When the connector is deleted, you see an error that the connection can't be found. At this point, the indexed files are also deleted. This is why you must reindex the files after re-authentication. - Repeat this pause|delete step for each connector. 2. Go back to the **Google Drive** Connector page (for example: http://localhost:3000/admin/connectors/google-drive) and click on **Revoke Access** to remove the stale OAuth credentials. 3. When the button changes to **Authenticate with Google Drive**, click on it to step through the OAuth flow again. 4. Add connectors back to start indexing again.
yindo commented 2026-02-15 17:05:33 -05:00
Author
Owner
Copy Link
Copy Source

@wenxi-onyx commented on GitHub (Jul 10, 2025):

@theship Thanks for the heads up on this. Can you clarify that this only happens for users without Google organizations (i.e. step 8 in the set up guide).

If so, we'll update the guides with a note on this.

@wenxi-onyx commented on GitHub (Jul 10, 2025): @theship Thanks for the heads up on this. Can you clarify that this only happens for users without Google organizations (i.e. step 8 in the set up guide). If so, we'll update the guides with a note on this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: onyx-dot-app/documentation#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?