Currently when a job status is sent to the browser via socket.io it's uniquely identified by the url + cron entry. Not a problem unless you have the same cron/url combination in different groups or in a waterfall you want the same URL run twice.
Currently when a job status is sent to the browser via socket.io it's uniquely identified by the url + cron entry.
Not a problem unless you have the same cron/url combination in different groups or in a waterfall you want the same URL run twice.