@Niall I am looking for some direction on this issue:
This issue is the final blocking issue to use the Camunda Job system for buffering messages. The short version is: There does not seem to be a way to create a failed job retry cycle without Activity Definition.
Okay i have solved the above issue with a workaround that injects some custom logic to create a in-mem activityImpl when the Retry cycle is being calculated.
@Dale_King@Niall, etc, What sort of retry cycle customizations that would normally want? I was thinking can just add a “handler” class with logic. Do you think this is desired to be a script level configuration or just a class instance? benefit of the script is you do not need to recompile.
No offense to Stephen’s work, but this does seem like a valuable part of the core product.
For all who are interested in “Message Queueing” getting into Camunda Platform, let’s upvote this feature request. https://jira.camunda.com/browse/CAM-13320