on ‎2018 Mar 08 1:38 PM
We have a number of custom workflows that have been working for years. Now we ran into a couple of cases where a workitem remains in status STARTED for no apparent reason.
The cases were created in two time windows of about 1.5 hours each, seemingly sporadically. For example, workitem 17389204 was stuck, but a couple of minutes later, another workitem 17389225 relating to the same task was created and processed successfully. All stuck workitems are for custom, synchronous background tasks.

There are no errors in ST22. There's no error, so SWWERRE won't pick the items up for reprocessing. Instead, they just remain STARTED, and due to that, won't process automatically.
I executed the workitems without check in SWIA, and the workflow continued normally. No urgent problem, but I'd like to know what could cause this. One guess of mine is that there were no background work processes available, but can't prove that post hoc.
The cases are rare: I've found 10 in total, while in the past 365 days, a good 400,000 workflows were processed successfully, each including several background tasks.
Given that the vast majority of cases work OK, I could say with confidence that the basic settings are OK, but I still cross-checked with Rick's blog.
Request clarification before answering.
Any dumps around that time?
Another common load-related issue might be RFC resources - see if anything is sitting in SM58
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 9 | |
| 7 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.