Introduce Cancelling state

[dradovic]

As explained in How to identify jobs that are being cancelled? cancellation of a job might take some time. It should be visible to users, when a job is being cacelled.

[Kyle_White]

Any update on this feature request? Would be very useful for I as well.

[dradovic]

Unfortunately not. But I’m glad to see that I’m not the only one.

[Kyle_White]

I noticed the developer has mentioned Hangfire should be customization enough to implement custom states. I am trying to come up with something but nothing notable yet…

Hangfire methods that dequeue and process requests

Hangfire is customizable a lot, but this concept is not well documented yet If you like to read the source code, you’ll receive the following ways to customize it: Add code before and after creating a background job (through client filters). Add code actions before and after performing a background job (through server filters). Please see CaptureCultureAttribute for example. Modify the state change pipeline, including introducing the new states (through state filters and custom states).…

[dradovic]

IMHO, a cancelling state is something that needs to be built into the system. No customization will help here because if that event is not a part of the event pipeline, it isn’t.

[alexandis]

I have the scenario, when based on specific condition, a given background job cannot be run again from UI. The OnPerforming handler is checking the condition and the job might be cancelled. I need to inform the user, why it is cancelled, but I cannot see an easy way to do this.