langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 09:10:05 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[Bug] Gmail Trigger works in Test Run but fails to activate in Published workflow #21983

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

Originally created by @kevintsai1202 on GitHub (Jan 29, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.11.4

Cloud or Self Hosted

Cloud

Steps to reproduce

The Gmail Trigger functions correctly when performing a "Test Run" (debug mode), successfully receiving the trigger and executing subsequent steps. However, once the workflow is Published, the Gmail Trigger stops responding to incoming emails.

Steps to reproduce

  1. Create a workflow including a Gmail Trigger.

  2. Execute a Test Run: The trigger receives the email and the workflow executes as expected.

  3. Publish the workflow.

  4. Send an email to the configured address.

  5. Observation: The workflow is not triggered, and no action is taken.

Additional Context
Other triggers within the same workflow (e.g., GitHub Trigger) continue to work normally after publishing; the issue seems specific to the Gmail Trigger.

✔️ Expected Behavior

The Gmail Trigger should function in the Published state exactly as it does during the Test Run, capturing events and initiating the workflow.

❌ Actual Behavior

After the workflow is published, the Gmail trigger does not receive events.

Originally created by @kevintsai1202 on GitHub (Jan 29, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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 [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.11.4 ### Cloud or Self Hosted Cloud ### Steps to reproduce The Gmail Trigger functions correctly when performing a "Test Run" (debug mode), successfully receiving the trigger and executing subsequent steps. However, once the workflow is Published, the Gmail Trigger stops responding to incoming emails. Steps to reproduce 1. Create a workflow including a Gmail Trigger. 2. Execute a Test Run: The trigger receives the email and the workflow executes as expected. 3. Publish the workflow. 4. Send an email to the configured address. 5. Observation: The workflow is not triggered, and no action is taken. Additional Context Other triggers within the same workflow (e.g., GitHub Trigger) continue to work normally after publishing; the issue seems specific to the Gmail Trigger. ### ✔️ Expected Behavior The Gmail Trigger should function in the Published state exactly as it does during the Test Run, capturing events and initiating the workflow. ### ❌ Actual Behavior After the workflow is published, the Gmail trigger does not receive events.
yindo added the 🐞 bugcloud labels 2026-02-21 20:15:09 -05:00
yindo commented 2026-02-21 20:15:09 -05:00
Author
Owner
Copy Link
Copy Source

@kevintsai1202 commented on GitHub (Feb 6, 2026):

any update?

@kevintsai1202 commented on GitHub (Feb 6, 2026): any update?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label cloud 🐞 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#21983
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?