conductor-oss / conductor-oss/conductor
UI: Tasks with taskReferenceName start cause the workflow to look strange when painted.
- Dominant language
- Java
- Stars
- 32.2k
- Forks
- 1k
- Avg merge
- 2d
- Merged PRs (30d)
- 33
Description
### Describe the bug
Tasks with taskReferenceName start cause the workflow to look strange when painted:
```json
{
"createTime": 1753342205564,
"updateTime": 0,
"name": "test",
"description": "test",
"version": 1,
"tasks": [
{
"name": "start",
"taskReferenceName": "start",
"inputParameters": {},
"type": "SIMPLE",
"decisionCases": {},
"defaultCase": [],
"forkTasks": [],
"startDelay": 0,
"joinOn": [],
"optional": false,
"defaultExclusiveJoinTask": [],
"asyncComplete": false,
"loopOver": [],
"onStateChange": {},
"permissive": false
}
],
"inputParameters": [],
"outputParameters": {},
"schemaVersion": 2,
"restartable": true,
"workflowStatusListenerEnabled": false,
"ownerEmail": "example@email.com",
"timeoutPolicy": "ALERT_ONLY",
"timeoutSeconds": 0,
"variables": {},
"inputTemplate": {},
"enforceSchema": true,
"metadata": {}
}
```
This can be seen both in the definition and in its execution:
Contributor guide
Assessment
This issue has not been assessed yet.