{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 小情绪 Triste * 的问题《Abandoned instances that will not continue executi》','https://www.manongdao.com/q-949784.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I have a lot of WF instances hosted in IIS/WAS which are in a running (idle) state which will not do anything even though they don't have such a long delay or any active bookmark.
Tracking is enabled (HealthMonitoringProfile).
As the tracking data is deleted, they end up without any tracked instance or events.
The only way to make them work again is to suspend and resume them, but this is sometimes failing and is always a pain.
Has anyone had this issue? any help?
Thanks in advance
In that case they are most likely triggering an error and abort leaving their state. As there is no trigger for them to start executing they just sit there and do nothing. The default option is to AbandonAndSuspend so you can resume them. You need to figure out what is causing them to fault and normally you can see that in the traced information.
Solution is here: AppFabric / WF 4.0 instances stuck despite no bookmark and pending timer