Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [Api] The up-stream process and task is shown error when import a dependent task #15493

Closed
3 tasks done
xiaolailong opened this issue Jan 16, 2024 · 3 comments
Closed
3 tasks done
Assignees
Labels
backend bug Something isn't working Stale

Comments

@xiaolailong
Copy link

Search before asking

  • 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:
1
2 (2)

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?

  • Yes I am willing to submit a PR!

Code of Conduct

@xiaolailong xiaolailong added bug Something isn't working Waiting for reply Waiting for reply labels Jan 16, 2024
@xiaolailong
Copy link
Author

xiaolailong commented Jan 16, 2024

pr is #15492

Copy link

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.

@github-actions github-actions bot added the Stale label Feb 17, 2024
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend bug Something isn't working Stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants