So this actually does put out 1 2 3 4 ... So it IS the same instance of my webapi, which I can tell by the singleton service. If it was a different instance, it would start at 0 every single time.
Now you should never do this, BUT that means hangfire jobs actually do work with application state somewhat. Obviously you cant guarantee your app hasnt restarted and hangfire executes a job right after. Even in FireAndForget scenarios.