Asp.Net Core Singleton being activated multiple times

I have a singleton registered in my startup.cs like so `services.AddSingleton();`. I also am adding hangfire and the service like so `services.AddHangfire(...)` and `services.AddHangfireServer(...)`. I know from looking at `HangfireServiceCollectionExtensions` that it should add the `AspNetCoreJobActivator` without me doing any extra work. That said, if I put a break point in the constructor of `TriggerWarmup` it gets hit once on app startup and then again when a job that targets it gets registered. Note, if i run that job multiple times after that initial run, the constructor doesn't get called again... so it seems like its kinda getting registered as a singleton but not really. Any thoughts?

Start with startup.cs and HangfireServiceCollectionExtensions, then trace how AspNetCoreJobActivator resolves TriggerWarmup during job registration and execution. Reproduce the constructor behavior described in the issue and determine whether the activation differs between application startup and the first targeted job. Done means the cause is identified and the singleton behavior is either corrected or clearly documented.

Written by the indexing model from the issue text.