Is there any why to set a Complex Repeating Task to only Repeat from end of invocation, like the Repeating Tasks With a Simple Interval. The problem is that the Complex Repeating Task kicks of the same service multiple times which is causing problems.
I have not found a way to do what you want, only workarounds to prevent multiple instances of the same service:
- You can set a lock within your flow which is removed at the end of the flow (or in case of an error).
- You can use “wm.server.query:getServiceStats” at the beginning of your flow to check if an instance is already running and exit in this case.
I am working with webMethods regarding an issue similar to this. They suggested using a java service that had a synchronized variable. Synchronized variables can be locked, so the first instance of a service will lock the variable, and then subsequent instances will detect the lock, until it is released. I’m not sure how this would work in a clustered environment.