langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Google Calendar Tool Fails with "Unknown Error" in Workflow #675

New Issue
Closed
opened 2026-02-16 10:20:09 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:20:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @y0ssh1 on GitHub (Sep 26, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues Dify issues & Dify Official Plugins, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.0

Plugin version

0.1.0

Cloud or Self Hosted

Cloud

Steps to reproduce

When using the Google Calendar tool in a workflow, it consistently fails with a generic "Unknown error". This issue occurs even in a minimal workflow designed solely to test the Google Calendar integration (e.g., Start -> Google Calendar -> End). The tool fails to execute any of its actions.

Image
  1. Create a new workflow.
  2. Add a Start node.
  3. Add a Google Calendar tool node.
  4. Configure the node to perform any action, such as "List Calendars" (カレンダー一覧を取得).
  5. Add an End node.
  6. Connect the nodes in sequence: Start -> Google Calendar -> End.
  7. Run a test of the workflow.
  8. Observe the execution log for the Google Calendar node, which will display an "Unknown error".

✔️ Error log

"Unknown error".

Image
Originally created by @y0ssh1 on GitHub (Sep 26, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.0 ### Plugin version 0.1.0 ### Cloud or Self Hosted Cloud ### Steps to reproduce When using the Google Calendar tool in a workflow, it consistently fails with a generic "Unknown error". This issue occurs even in a minimal workflow designed solely to test the Google Calendar integration (e.g., Start -> Google Calendar -> End). The tool fails to execute any of its actions. <img width="1065" height="202" alt="Image" src="https://github.com/user-attachments/assets/d0a9e22e-bee1-4066-b34f-9b27e85fb16f" /> 1. Create a new workflow. 2. Add a **Start** node. 3. Add a **Google Calendar** tool node. 4. Configure the node to perform any action, such as "List Calendars" (`カレンダー一覧を取得`). 5. Add an **End** node. 6. Connect the nodes in sequence: `Start` -> `Google Calendar` -> `End`. 7. Run a test of the workflow. 8. Observe the execution log for the Google Calendar node, which will display an "Unknown error". ### ✔️ Error log "Unknown error". <img width="904" height="781" alt="Image" src="https://github.com/user-attachments/assets/165ff8f3-60dd-49af-a341-7bf75edf64d8" />
yindo added the bug label 2026-02-16 10:20:09 -05:00
yindo closed this issue 2026-02-16 10:20:09 -05:00
yindo commented 2026-02-16 10:20:09 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 26, 2025):

Hi @y0ssh1! I'm Dosu and I’m helping the dify-official-plugins team.

The Google Calendar tool's "Unknown error" is usually triggered when the plugin encounters unexpected issues like missing or invalid OAuth credentials, insufficient API permissions, or network problems. The code checks for a valid access_token and specific API errors (401 for authentication, 403 for permissions), but any other error—including misconfiguration or connectivity issues—gets caught by a generic exception handler and reported as "Unknown error" in the workflow log, which can obscure the real cause.

To troubleshoot, double-check that your Google OAuth credentials are correctly configured, the access token is valid, the required Calendar API scopes are granted, and your cloud environment can reach Google's API endpoints. Improving credential setup or network access often resolves these generic failures. More detailed error reporting could help, but currently, most unexpected issues are surfaced as "Unknown error" due to catch-all exception handling in the plugin code [source].

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 26, 2025): <!-- Greeting --> Hi @y0ssh1! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. <!-- Answer --> The Google Calendar tool's "Unknown error" is usually triggered when the plugin encounters unexpected issues like missing or invalid OAuth credentials, insufficient API permissions, or network problems. The code checks for a valid `access_token` and specific API errors (401 for authentication, 403 for permissions), but any other error—including misconfiguration or connectivity issues—gets caught by a generic exception handler and reported as "Unknown error" in the workflow log, which can obscure the real cause. To troubleshoot, double-check that your Google OAuth credentials are correctly configured, the access token is valid, the required Calendar API scopes are granted, and your cloud environment can reach Google's API endpoints. Improving credential setup or network access often resolves these generic failures. More detailed error reporting could help, but currently, most unexpected issues are surfaced as "Unknown error" due to catch-all exception handling in the plugin code [[source](https://github.com/langgenius/dify-official-plugins/blob/246dfdd965a9648317ef2e8a152c4a683b0138f2/tools/google_calendar/tools/list_calendars.py)]. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/2d836bd1-bce5-4a91-a627-86f1d2fdf3ed?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2d836bd1-bce5-4a91-a627-86f1d2fdf3ed?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2d836bd1-bce5-4a91-a627-86f1d2fdf3ed?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2d836bd1-bce5-4a91-a627-86f1d2fdf3ed?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2d836bd1-bce5-4a91-a627-86f1d2fdf3ed?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/2d836bd1-bce5-4a91-a627-86f1d2fdf3ed?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2d836bd1-bce5-4a91-a627-86f1d2fdf3ed?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1777)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug
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: langgenius/dify-official-plugins#675
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?