[Bug] [MASTER SERVER] task run failed，master server prompt NPE(3.1.7)

[Anubisxcw]

Search before asking

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

What happened

My workflow defines a shell task that will use many custom parameters, many resource center files.
When I run the workflow, no task instance is generated, and also when I click in the workflow instance screen to see the log of the shell task, there is no log button.
When I click on stop workflow, it keeps getting stuck in the ready to stop state.
At the same time master's logs are growing fast

What you expected to happen

i do not care the log or the workflow bug.i just want the task can run .
Same shell task. This problem does not occur when I create new projects, workflows and tasks.
But it does it a few more times I run it, as soon as it appears the first time. After that, it keeps happening when I run the task. This causes my shell task to not run and blocks my core workflow.
I just wish I could get a quick way around this bug, like modifying the database etc.

How to reproduce

1.run the work flow
2.then you can see the there is not a taskinstance.
3.the log will flash

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

• 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

[Anubisxcw]

我绕过了这个bug。首先在任务节点里把资源中心引入的文件删了，然后资源中心重新上传更改后的，在重新引用。
这个bug我估计是有人没更改任务节点，只在资源中心重新上查了同名文件。但是文件ID变了。所以执行任务时当然空指针了。

[HomminLee]

@Anubisxcw This issue is very similar to #13980 (comment), but it was fixed at 3.1.6. Maybe can provide you with some ideas.

[github-actions]

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]

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.