add the partial-succeed status of workflows #613
Conversation
dosubot
bot
added
the
size:XS
There was a problem hiding this comment.
Pull request overview
This PR adds support for the "partial-succeeded" status to workflow execution results across the API documentation. The change extends the workflow status enum to better represent scenarios where a workflow completes execution but encounters issues in some of its steps, distinguishing this from complete success or complete failure.
Key Changes:
- Extended the
WorkflowFinishedDatastatus enum to include "partial-succeeded" alongside existing statuses ("running", "succeeded", "failed", "stopped") - Updated consistently across all three language versions (English, Chinese, and Japanese)
- Appropriately limited to workflow-level status; node-level status remains unchanged
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| en/api-reference/openapi_workflow.json | Added "partial-succeeded" to WorkflowFinishedData status enum |
| zh/api-reference/openapi_workflow.json | Added "partial-succeeded" to WorkflowFinishedDataCn status enum (Chinese translation) |
| ja/api-reference/openapi_workflow.json | Added "partial-succeeded" to WorkflowFinishedDataJp status enum (Japanese translation) |
The changes are consistent, well-structured, and semantically appropriate. The PR correctly distinguishes between workflow-level execution status (which can be partial) and node-level execution status (which remains binary), demonstrating sound API design principles.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
No description provided.