Google Plugin Invocation Error – 403 PERMISSION_DENIED #84

Closed
opened 2026-02-16 00:19:40 -05:00 by yindo · 2 comments
Owner

Originally created by @cj-murillo on GitHub (Apr 10, 2025).

Dify Plugin Daemon Version -> 0.0.7
Description
When invoking the Google plugin, an error occurs preventing access to a specific file. This may be due to insufficient permissions or the file being nonexistent. The error message returned is as follows:

[google] Error: PluginInvokeError: { "args": {}, "error_type": "ClientError", "message": "403 PERMISSION_DENIED. { 'error': { 'code': 403, 'message': 'You do not have permission to access the File xxxxxxxxx or it may not exist.', 'status': 'PERMISSION_DENIED' } }" }

Notes
The issue appears to be related to file-level access permissions or misidentification of the file.

Please review the handling of permissions and ensure proper validation of file existence and access rights.

Originally created by @cj-murillo on GitHub (Apr 10, 2025). Dify Plugin Daemon Version -> 0.0.7 Description When invoking the Google plugin, an error occurs preventing access to a specific file. This may be due to insufficient permissions or the file being nonexistent. The error message returned is as follows: `[google] Error: PluginInvokeError: { "args": {}, "error_type": "ClientError", "message": "403 PERMISSION_DENIED. { 'error': { 'code': 403, 'message': 'You do not have permission to access the File xxxxxxxxx or it may not exist.', 'status': 'PERMISSION_DENIED' } }" }` Notes The issue appears to be related to file-level access permissions or misidentification of the file. Please review the handling of permissions and ensure proper validation of file existence and access rights.
yindo closed this issue 2026-02-16 00:19:40 -05:00
Author
Owner

@Yeuoly commented on GitHub (Apr 11, 2025):

This should not be an issue of daemon, this message dose not exist in our repo and the most possible reason is plugin itself raises it

@Yeuoly commented on GitHub (Apr 11, 2025): This should not be an issue of daemon, this message dose not exist in our repo and the most possible reason is plugin itself raises it
Author
Owner

@cj-murillo commented on GitHub (Apr 14, 2025):

Thanks for the clarification! That makes sense — closing the issue now. 🙌

@cj-murillo commented on GitHub (Apr 14, 2025): Thanks for the clarification! That makes sense — closing the issue now. 🙌
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#84