Hello,
Here is my issue :
I have a loop iterating X times on a webservice call (the SalesForce way, for those who know : the number of lines returned by the WBS is limited, and SalesForce sends a "NextURL" in each webservice call).
Sometimes, one of these calls bugs, and stays "RUNNING" indefinitely, with many consequences :
- The next scheduled execution doesn't start (cause the previous one is still running ?). Deleting the corresponding line in the log database does not solve this : I guess that's there is something still "running" at runtime level (no return code received, something like that ?).
- It's impossible to stop it through the analytics (right click > "Stop" action does not do anything)
For now, my only solution is to restart the runtime (with a kill command : I can't stop it properly, maybe because of this "ghost running session" ?).
As far as i noticed, it can happen on different webservices, after a variable number of iterations (sometimes 1, sometimes 50).
This "randomness" and the small quantity of "log" on the "Call WebServices" step make the analysis kinda hard.
Unless someone already faced this issue and found a solution, I think that I could handle this by adding a "timeout" somewhere, on the mapping, or at a process level, so that if the call does not respond after, for example, 30sec, it falls in error, and go to the next iteration.
Is there a way to do this ?
For now, we are using a 17.4.2 runtime / S19 Designer (our migration to S20.X Designer / Runtime is scheduled in the coming weeks)
Thanks, and nice holidays !
