fix(drive-integration): handle google-docs-not-found workflow failure []#10998
Open
Mitch Goudy (mgoudy91) wants to merge 2 commits into
Open
fix(drive-integration): handle google-docs-not-found workflow failure []#10998Mitch Goudy (mgoudy91) wants to merge 2 commits into
Mitch Goudy (mgoudy91) wants to merge 2 commits into
Conversation
Mitch Goudy (mgoudy91)
changed the title
Mitch Goudy (mgoudy91)
force-pushed
the
fix/google-docs-404-not-found
branch
from
06b0e9f to
e583b42
Compare
… reason Adds GOOGLE_DOCS_NOT_FOUND to WorkflowFailureReason and wires it through the hook and error modal so users see "Document not found" with an actionable message instead of the generic error screen. Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
…v vars GOOGLE_PICKER_API_KEY and GOOGLE_APP_ID were hardcoded (empty string and 1 respectively), causing the Google Picker to not reliably show files the user owns — especially newly created docs. Reads from VITE_GOOGLE_PICKER_API_KEY and VITE_GOOGLE_APP_ID env vars instead, and wires them into CI build steps. The actual values must be added to CircleCI project environment variables: - VITE_GOOGLE_PICKER_API_KEY: from GCP > APIs & Services > Credentials > Drive Integration API key - VITE_GOOGLE_APP_ID: 991777691184 (Contentful Google Docs App project number) Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Mitch Goudy (mgoudy91)
force-pushed
the
fix/google-docs-404-not-found
branch
from
e583b42 to
f5a2897
Compare
Joaquin (joaquincasal)
approved these changes
May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GOOGLE_DOCS_NOT_FOUNDtoWorkflowFailureReasonenumuseWorkflowAgenthook andModalOrchestratorso users see "Document not found" with an actionable message instead of the generic error screenWhat changed
workflow.ts: newGOOGLE_DOCS_NOT_FOUNDenum valuemessages.ts: newGOOGLE_DOCS_NOT_FOUNDerror messageuseWorkflowAgent.ts: recognizes the new failure code and returns the specific messageModalOrchestrator.tsx: handles the new reason inshowWorkflowError, renders modal with title "Document not found"Companion PR
Requires backend change in
contentful/agents-api: https://github.com/contentful/agents-api/pull/538Test plan
🤖 Generated with Claude Code