After starting the workflow, the entries in the WfPropagationQueue queue are always in the Executing state.

[ZL_10925195]

I am using Windchill PDMLink Release 11.0 and Datecode with CPS M030-CPS15 

After starting the workflow, the entries in the WfPropagationQueue queue are always in the Executing state, and the BackgroundMsthodServer does not report an error log. After waiting for about ten minutes, the entries are completed and the workflow flows to the next node.
--------------------------------------------
Translated text from Simplified Chinese to English using google translate

Subject  - 启动工作流后，WfPropagationQueue队列中的条目一直是Executing状态
Body - 启动工作流后，在WfPropagationQueue队列中的条目一直是Executing状态，且BackgroundMsthodServer没有报错日志，等待大概十分钟后，条目才执行完毕，工作流流转到下一节点
--------------------------------------------

[Rocket_Max]

Hi @ZL_10925195 

• Clear workflow cache
  • Delete cache files under <WindchillHome>\codebase\wt\workflow\expr
• Restart Background Method Server

[ZL_10925195]

I have tried, but it didn't work.

[Rocket_Max]

Hi @ZL_10925195 

• Check the process logic, is there any condition that is not met?
• How is Windchill's performance when this phenomenon occurs?
• Are all the processes like this? Or something else?
• Is database communication normal?
• Grab the thread dump to see the thread 

  https://www.ptc.com/cn/support/article/CS115335?art_lang=en

[HelesicPetr]

Hi @ZL_10925195 

What is the question? Why the entries are still in executing state even though the workflow has been finished? 

PetrH

[Rocket_Max]

Hi @HelesicPetr 

There is a problem with the translation...

His meaning is that the queue entry will only be executed ten minutes after the workflow task starts, rather than immediately executing it

[ZL_10925195]

Simultaneously in the database, there will be INACTIVE locks on the SCHEDULEQUEUEENTRY, WFCONNECTOR, WFASSIGNMENT, WFASSIGNEDACTIVITY, WORKITEM, and WFEXPRESSION tables.

[Rocket_Max]

Hi @ZL_10925195 

From your description, it seems that there has been a competition for resources
Can the problem be stably reproduced?
Will the problem disappear if Windchill and the database are restarted?

[ZL_10925195]

 the problem can be stably reproduced

Both Windchill and the database have been restarted, but the problem still persists.

[Rocket_Max]

Hi @ZL_10925195 

Check the workflow logic and grabbing thread dump

It should be caused by resource locking

[HelesicPetr]

Oh ok.

Then it is problem with performance usually. 

PetrH

[ZL_10925195]

No，

The issue is not with performance; everything else works fine except for the workflow.