[Bug] [Module Name] Starting the workflow, the global variable cannot obtain the incoming parameters while waiting for the flow in serial waiting mode according to the execution strategy
Search before asking
- [x] I had searched in the issues and found no similar issues.
What happened
3.1.4版本 调用api 运行实例接口 启动工作流实例,发现 在执行策略为串行等待 模式下等待流无法获取传入参数。
What you expected to happen
调用命令:
curl --location 'http://10.0.1.106:12345/dolphinscheduler/projects/16631684081664/executors/start-process-instance'
--header 'Accept: application/json, text/plain, /'
--header 'Accept-Language: zh-CN,zh;q=0.9'
--header 'Cache-Control: no-cache'
--header 'Connection: keep-alive'
--header 'Content-Type: application/x-www-form-urlencoded'
--header 'Pragma: no-cache'
--header 'token: f4755fae084dea54ef38103b10abc941'
--data-urlencode 'processDefinitionCode=16649316257664'
--data-urlencode 'failureStrategy=CONTINUE'
--data-urlencode 'warningType=FAILURE'
--data-urlencode 'processInstancePriority=HIGHEST'
--data-urlencode 'startParams={"var":"22222"}'
--data-urlencode 'dryRun=0'
--data-urlencode 'scheduleTime='
How to reproduce
脚本截图:
流程配置截图:
调用命令:
curl --location 'http://10.0.1.106:12345/dolphinscheduler/projects/16631684081664/executors/start-process-instance'
--header 'Accept: application/json, text/plain, /'
--header 'Accept-Language: zh-CN,zh;q=0.9'
--header 'Cache-Control: no-cache'
--header 'Connection: keep-alive'
--header 'Content-Type: application/x-www-form-urlencoded'
--header 'Pragma: no-cache'
--header 'token: f4755fae084dea54ef38103b10abc941'
--data-urlencode 'processDefinitionCode=16649316257664'
--data-urlencode 'failureStrategy=CONTINUE'
--data-urlencode 'warningType=FAILURE'
--data-urlencode 'processInstancePriority=HIGHEST'
--data-urlencode 'startParams={"var":"22222"}'
--data-urlencode 'dryRun=0'
--data-urlencode 'scheduleTime='
调用结果: 第一次调用打印
第二次调用
Anything else
No response
Version
3.1.x
Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Search before asking
- [x] I had searched in the issues and found no similar issues.
What happened
Version 3.1.4 Call API Run the instance interface Start the workflow instance and found that waiting for the stream cannot obtain incoming parameters when the execution policy is serial waiting mode.
What you expected to happen
Call the command:
curl --location 'http://10.0.1.106:12345/dolphinscheduler/projects/16631684081664/executors/start-process-instance'
--header 'Accept: application/json, text/plain, /'
--header 'Accept-Language: zh-CN,zh;q=0.9'
--header 'Cache-Control: no-cache'
--header 'Connection: keep-alive'
--header 'Content-Type: application/x-www-form-urlencoded'
--header 'Pragma: no-cache'
--header 'token: f4755fae084dea54ef38103b10abc941'
--data-urlencode 'processDefinitionCode=16649316257664'
--data-urlencode 'failureStrategy=CONTINUE'
--data-urlencode 'warningType=FAILURE'
--data-urlencode 'processInstancePriority=HIGHEST'
--data-urlencode 'startParams={"var":"22222"}'
--data-urlencode 'dryRun=0'
--data-urlencode 'scheduleTime='
How to reproduce
Script screenshot:
Screenshot of process configuration:
Call the command:
curl --location 'http://10.0.1.106:12345/dolphinscheduler/projects/16631684081664/executors/start-process-instance'
--header 'Accept: application/json, text/plain, /'
--header 'Accept-Language: zh-CN,zh;q=0.9'
--header 'Cache-Control: no-cache'
--header 'Connection: keep-alive'
--header 'Content-Type: application/x-www-form-urlencoded'
--header 'Pragma: no-cache'
--header 'token: f4755fae084dea54ef38103b10abc941'
--data-urlencode 'processDefinitionCode=16649316257664'
--data-urlencode 'failureStrategy=CONTINUE'
--data-urlencode 'warningType=FAILURE'
--data-urlencode 'processInstancePriority=HIGHEST'
--data-urlencode 'startParams={"var":"22222"}'
--data-urlencode 'dryRun=0'
--data-urlencode 'scheduleTime='
Call result: First call to print
The second call
Anything else
No response
Version
3.1.x
Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Hi @SbloodyS i am willing to take this