Hangfire: Can not change the state to 'Processing': target method was not found

[sabiland]

I see a lot of those messages in Hangfire Retries tab.
Can not change the state to 'Processing': target method was not found

We run 2-identical Web Applications on 2 servers (ASP Net Core) and use MSSQL for Hangfire storage.
I think that the enqueued job is even correctly finished, but anyways the message "target method was not found" appears in Hangfire dashboard.

[rsilvanet]

Hi @sabiland,

Here are described some reasons for this error message. In my experience with hangfire, it really happened sometimes when we changed methods declaration, so Hangfire couldn't proceed with already enqueued jobs that were serialized with the old declaration. Does that make sense for your case?

Hope it's helpful 😄

[sabiland]

@rsilvanet I will check your link.

@rsilvanet I most surely do not change method signature, because it is unchanged for more than a year now.

Could maybe changes (impossible I guess, but anyways) in the same .cs file and then building/publishing have any effect on this "target method was not found" ?

And I would like to ask another question: Can default retry attempts (=10) for Hangfire Internal exceptions be configured?