You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
When import a dependent task from a Json file in a new environment that export by a old environment, the import operation is success, but you will get error message like "get task list by process definition id error", when you open the detail page about the import dependent task.
Following is the error screenshot:
What you expected to happen
After importing a dependent task from Json file, the up-stream process and task should link properly.
How to reproduce
Import from the example Json file, and open the detail page of the dependent task of llow3 in the api ui, you will see some error message which show the up-stream process and task not link properly. workflow_1705391814549.json
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.
Search before asking
What happened
When import a dependent task from a Json file in a new environment that export by a old environment, the import operation is success, but you will get error message like "get task list by process definition id error", when you open the detail page about the import dependent task.
Following is the error screenshot:
What you expected to happen
After importing a dependent task from Json file, the up-stream process and task should link properly.
How to reproduce
Import from the example Json file, and open the detail page of the dependent task of llow3 in the api ui, you will see some error message which show the up-stream process and task not link properly.
workflow_1705391814549.json
Anything else
No response
Version
dev
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: