I often need a workflow that calls itself forever in order to develop on webinterface and similar tests.
Here is a simple workflow that calls itself forever. It is too fast to be cancelled from UI, for that you can add hold 10 seconds instead of 0 seconds.
It uses a http communicate processor to start a new API job to it's own workflow ID and also it sets and submits the current loop count as a variable.
So after all this is also a good example how to start another workflow using the http communicate processor in case you need that.
Workflow example: loop forever
Workflow example: loop forever
emcodem, wrapping since 2009 you got the rhyme?