What is the current best practice or is there any roadmap for signalling workers from workflows or activities?
Our use case is to suspend polling in case e.g. the target system needs to undergo maintenance and any interaction is unwanted. This is usually done by users triggering something e.g. in a ticketing system… which would be neat to implement as a workflow by itself. The challenge is that the target system is accessed from Activities served by a dedicated worker (that can be e.g. placed in a specific network segment).
As per what I have read there is no method to access workers or their factories from any central point.
Based on available options I think a partial solution could be to have each worker registering a SignalWorkflow that would actually sleep forever but would implement a SignalMethod that would access the bootstrap class e.g. by having it as singleton. Then the challenge would be to have at least one SignalWorkflow running on each worker. It’s not really nice but in our case it could work because we have only one worker accessing the target system so we know that the SignalMethod will be run on that specific worker everytime.
It would definitely be better to have some way to signal e.g. all workers who have registered a specific Activity interface.