Can you elaborate why Polly is a pain to debug?

[jzabroski]

Thanks for this library.

[SanderSade]

Coworker was using Polly to handle a complex, multi-part operation - and on occasion Polly simply did not re-try. I cannot remember for sure, but think in the end he traced it to a faulty Polly setup, but it took him a long, long while to find the issue. That said, I still think that Polly is a most excellent library, and heartily recommend it.

And you're most welcome!

[jzabroski]

Can we ask him to share his experience here? :)

Just curious for two reasons:

1. To improve as an engineer. Planning to recommend Polly at work.
2. I'm also currently helping Microsoft improve the documentation around HttpClient. See: Warning about incorrect lifecycle policy dotnet/dotnet-api-docs#2315 - Currently, Microsoft unofficially (but officially in the sense their best practices documentation says use Polly) recommends Polly for transient fault handling.

[SanderSade]

I actually think Polly is more popular outside MS then in-house - largely still due to that damn old NIH (Not Invented Here) syndrome that we as a company have...

Just talked with the coworker - he cannot remember for sure, but thinks it was when he upgraded Polly to a newer version then retries stopped working without any error messages (both compilation & runtime). Once he got it back to work it was flawless, so he has used it again in other projects.

[SanderSade]

Going to close this, no new questions/comments