What are the conditions that trigger the partial-succeeded status?

[shelic-A]

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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

We are trying to integrate our backend system with the Dify workflow. The response needs to include a status code so that we can handle subsequent processing, so we decided to use the existing status field in the current response structure.

However, during one API request test, we encountered a partial-succeeded status. When we immediately repeated the request locally, the returned status became succeeded.

We were unable to find any clear triggering conditions for partial-succeeded in either the API documentation or community discussions, so for now we have to treat this status as a failure to mitigate risk. It would be very helpful if the triggering logic for this status could be clarified.

Test response:
{"task_id": "8e2f4030-81ff-4b9d-9878-8aac8711954b", "workflow_run_id": "d6a5a293-d276-4b27-bee7-00a655168579", "data": {"id": "d6a5a293-d276-4b27-bee7-00a655168579", "w
orkflow_id": "7c9df78b-e68d-458c-9deb-584fb7640f71", "status": "partial-succeeded", "outputs": {"email_type": "\u5176\u4ed6"}, "error": null, "elapsed_time": 19.944407, "total_tokens": 796, "total_steps": 7, "created
_at": 1768281186, "finished_at": 1768281206}}

2. Additional context or comments

No response

[dosubot[bot]]

Hi @shelic-A! I'm Dosu and I’m helping the dify team.

The partial-succeeded status is triggered when errors occur during workflow execution, but those errors are handled by error strategies defined in the workflow—such as using a "fail branch" or a "default value" for a failed step. This means some parts of the workflow completed successfully, while others encountered recoverable errors that did not cause a full failure. The status is a terminal state, distinct from succeeded and failed, and was introduced in Dify v1.10.0. The current documentation does not fully explain this status yet, but maintainers have confirmed its meaning and plan to clarify it in future updates. For more details, see the code comments and maintainer explanation and the workflow status enum.

To reply, just mention @dosu.

---

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

   

[shelic-A]

Thank you for your detailed explanation. That was very helpful. We will follow this process and run another round of tests. If we encounter any further issues, we will report back. Thanks again!