After I upgraded from 3.1.8 to 3.2.0, I could not find the workflow instance after creating tasks in the workflow definition and clicking Run.

[1498658503]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

After I upgraded from 3.1.8 to 3.2.0, I could not find the workflow instance after creating tasks in the workflow definition and clicking "run". I checked the database table, and found that a data was inserted into the t_ds_process_instance table, but the project_code was null. Moreover, the task instance of the task I created in 3.1.8 had the same project_code, which could not be found.

What you expected to happen

Clicking Run will show that the foreground is successful, and the background will not report an error. When I upgraded, I executed the upgraded ddl and dml sql scripts, and also tried to rebuild the database, but this situation still exists

How to reproduce

1

Anything else

No response

Version

3.2.x

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[1498658503]

[ruanwenjun]

Have you execute the upgrade tools? In 3.2.0 we add a new column project_code in t_ds_process_instance.

[samael0119]

类似的问题，我用helm安装了全新的3.2.0版本后，运行一个工作流提示成功，但是实例列表没内容

[1498658503]

Have you execute the upgrade tools? In 3.2.0 we add a new column project_code in t_ds_process_instance.

t_ds_process_instance already has a project_code field, but there is no new instance data in the table.

[truonglac2603]

类似的问题，我用helm安装了全新的3.2.0版本后，运行一个工作流提示成功，但是实例列表没内容

facing the same issue, if you check the log of workers, there may be errors indicate that current cpu load average is overload or available memory is insufficient. Related to this discussion: https://github.com/apache/dolphinscheduler/discussions/15047#discussion-5752268