Inconsistency regarding Multiple Triggers support between Documentation/Pricing and SaaS Behavior

[yangzq50]

Self Checks

• I have searched for existing issues search for existing issues, 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.

Content

Descriptions

There is a significant inconsistency between the Dify documentation (including pricing), the actual behavior on Dify SaaS, and recent developer explanations regarding the support for multiple triggers in a single workflow.

Environment

• Platform: Dify SaaS (https://cloud.dify.ai/)
• Version: 1.11.2

Details

1. Documentation & Pricing Claims:
The Dify Documentation states:

"A workflow can have multiple triggers running in parallel. You can also build several independent workflows on the same canvas..."
"The Sandbox plan supports up to 2 triggers per workflow."

Additionally, the Pricing Page indicates that the Professional plan supports unlimited triggers per workflow.

2. Observed Behavior:
When attempting to add two triggers to a single workflow on the SaaS platform, only the first trigger added remains enabled. The second trigger appears to be disabled or non-functional. This aligns with behavior reported by other users in Issue #29038.

3. Developer Context:
In a related Pull Request (#29982), a Dify developer commented that allowing users to add multiple schedule nodes was actually considered a frontend bug, suggesting that multiple triggers (or at least multiple schedule triggers) might not be fully supported by design.

Expected Behavior

The documentation and pricing page should accurately reflect the platform's actual capabilities.

• If multiple triggers are supported, the feature should work as described (allowing multiple active triggers).
• If multiple triggers are not supported (or limited to specific types), the documentation and pricing page should be updated to remove the misleading claims about "multiple triggers running in parallel" and "unlimited triggers" availability.

Related Links

• Existing User Report: When adding multiple scheduled triggers, they do not trigger correctly, but only one of them is triggered. #29038
• Developer Comment: fix(schedule): support multiple schedule triggers in workflow #29982

[yangzq50]

Hi @Yeuoly, I'm tagging you here to help clarify the inconsistency mentioned above regarding the support for multiple parallel triggers. Would appreciate your input!

[dosubot[bot]]

The current backend only supports a single schedule trigger per workflow—when you add multiple schedule triggers, only the first one is executed and the rest are ignored. This is intentional and confirmed by both the code and recent developer comments: allowing multiple schedule nodes is considered a frontend bug, not a supported feature. The recommended approach for complex scheduling is to use multiple cron expressions within a single schedule node, or to split your logic into separate apps if you need multiple independent flows. Plugin triggers (non-schedule) are supported up to 5 per workflow, but this does not apply to schedule triggers. The documentation and pricing currently overstate the support for multiple schedule triggers, and there’s no indication this will change soon—so for now, rely on the current backend behavior and suggested workarounds.
See developer comment and code references
Backend logic details
Related user report

To reply, just mention @dosu.

---

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

   

[yangzq50]

Attached is a screenshot from Dify SaaS showing the behavior. I am on the Professional plan, which according to the pricing page should support "Unlimited triggers per workflow."

As you can see, even though the second trigger was scheduled for an earlier time, it did not execute. Only the first trigger I added to the workflow actually runs, while the second one remains inactive despite its settings.

[yangzq50]

Hi @RiskeyL, tagging you here as the author of the documentation regarding multiple triggers. We are discussing some inconsistencies between the current documentation and the actual SaaS behavior, and would appreciate your input!

[RiskeyL]

Hi @yangzq50, thanks for catching this! At the moment, a single workflow does indeed support adding at most one schedule trigger. The doc has been updated, and the frontend will get fixed too.

[yangzq50]

Regarding #29943—@Yeuoly, what are your thoughts on this: if the decision is to limit one workflow to a single trigger, it could actually simplify the trigger debugging process in the future as there would be no need to wait for parallel conditions. With multiple triggers, the exact execution starting point becomes much harder to identify.