[Bug] [3.0.0] process-definition has to be started a second time every time

[bdxmq]

Search before asking

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

What happened

The process is invalid the first time it is started, and it has to be started a second time every time.
The first startup shows success, but the instance is not running, the second startup is fine.

What you expected to happen

Hope it gets resolved

How to reproduce

1

Anything else

No response

Version

3.0.0

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

[github-actions]

Thank you for your feedback, we have received your issue, Please wait patiently for a reply.

• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can join our slack and send your question to channel #troubleshooting

[SbloodyS]

Could you describe it more specifically? @bdxmq

[bdxmq]

--process-definition--
The first time I click run, it shows success, but there are no workflows and tasks running in the view instance. The second time I click run, the workflow and tasks can run normally

[SbloodyS]

--process-definition-- The first time I click run, it shows success, but there are no workflows and tasks running in the view instance. The second time I click run, the workflow and tasks can run normally

Could you check if there is any valid information in the logs?

[bdxmq]

Now it's ok. I found that my colleagues installed the old version according to the installation method, and did not change the configuration of the service, including application.yaml and common.properties. The old version does not need to be changed after it is configured in install. Now that the configuration is changed, there is no problem. Sorry, our problem.

[SbloodyS]

Glad to here that. I'll close this issue.