Issues with multiple applications accessing the same hangfire db.

We're having issues on our local environment where there are two applications installed one on my machine and another on my co-worker's. So two IIS instances hitting the same hangfire database. On the documentation it provides a code to handle this but when writing the code it says that server name is deprecated and that it handles it in the backend already. Now that's not word for word but that's the idea. Our issue is when debugging code from one machine hangfire fires the job that's on the other machine, never hitting the breakpoint from the code it's being fired from. For the moment we created separate hangfire databases and it solves it but is there another way? Like a setting that I can change/include so that hangfire can handle multiple apps with one hf db?

Start with the documentation guidance about server names and the reported behavior when two IIS instances share one Hangfire database. Reproduce the debugging scenario with two applications and compare it with the separate-database workaround; done means the supported shared-database configuration and its effect on job execution are clearly documented or confirmed.

Written by the indexing model from the issue text.