[Bug] Gmail trigger output variables are lost after exiting and re-opening the workflow.

[kevintsai1202]

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

After configuring and testing the Gmail trigger workflow, the output variables disappear when I exit and re-enter the workflow, and the flow no longer functions correctly.

✔️ Expected Behavior

❌ Actual Behavior

[dosubot]

This bug is already tracked and recognized by maintainers as a state persistence issue with Gmail trigger output variables in workflows—see issue #1542. The root cause is that output variables for Gmail triggers are built dynamically from the plugin’s output schema in the frontend, but this schema isn’t persisted with the workflow node, so variables disappear when you reload the workflow editor. The backend only saves execution outputs for tracing, not for restoring the design-time schema, which is why the problem occurs source.

Recent updates have improved general workflow and variable persistence (PR #30300, PR #30531), but none specifically fix this Gmail trigger issue. In v1.11.4, stricter backend validation now requires every workflow node output to include a value_type field; missing this can cause variables to disappear or block workflow saving, and this affects both new and existing workflows—not just Gmail triggers (related regression).

There’s no official workaround yet. For similar variable persistence issues, some users have had partial success by re-importing nodes or resetting variables, but this isn’t guaranteed to fix the Gmail trigger output variable loss. If you want to help maintainers diagnose or prioritize a fix, sharing your workflow export, error logs, or detailed steps to reproduce can be useful.

Keep an eye on issue #1542 for updates.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[kevintsai1202]

DSL
gmail.yml

[tnfsmith]

yeah, Dify experience with bug variable does not update corresponding changes back/frontend. I also report this bug in v1.11.3. You can make any edit but when you out/in this workflow it display error lack of this variable, the node did not displace variable.

[kevintsai1202]

@hyoban
The bug still exists