Can an exception be thrown if the processing time on the timer is too long？

[kengiczhangchao]

Can an exception be thrown if the processing time on the timer is too long.

Settings similar to the following
.Configure(options =>
{
options.ResponseTimeout = TimeSpan.FromSeconds(30);
})

[ReubenBond]

@kengiczhangchao there is no response for a timer execution, so there would be nothing to catch the exception. This is true for timers in .NET in general: there is no call site in user code where the exception can be propagated to.

Given the above, what would you like to see in the case that a timer callback exceeds its time limit? It should be straightforward to implement something.

[kengiczhangchao]

@kengiczhangchao there is no response for a timer execution, so there would be nothing to catch the exception. This is true for timers in .NET in general: there is no call site in user code where the exception can be propagated to.

Given the above, what would you like to see in the case that a timer callback exceeds its time limit? It should be straightforward to implement something.
I hope throw an exception when a task is executed too long time in callback and then continue with the next callback instead of waiting all the time，The grain seems to be dead，And the program doesn't know what went wrong。

[kengiczhangchao]

@ReubenBond

[ReubenBond]

@kengiczhangchao could you show me roughly what the timer task is doing? If it is running forever, that is a problem. Grains are single-threaded and cancellation in .NET is cooperative (the callee must check the CancellationToken themselves), so it cannot just abandon a long-running operation and let it keep going without the operation cooperating. Does that make sense? Otherwise, the task could keep going in the background. If we stopped the task from executing altogether, then any resources which it holds (eg, locks/semaphores) will not be released. This is why it is not valid in .NET to abandon a running method, because catch/finally/cleanup blocks would not be executed