> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/development/hangfire.md). # Hangfire View the Hangfire job execution dashboard in PowerShell Universal to diagnose scheduled jobs, running jobs, and failures affecting automation execution. [Hangfire](https://www.hangfire.io/) is the scheduling library that PowerShell Universal uses to execute and schedule jobs. It may be useful to view the status of the Hangfire job execution queues. This is typically useful if you have jobs that aren't running or schedules not starting at the proper times. You can access the Job Details dashboard by clicking the Diagnostics button in **Run > Jobs**. ## Scheduled Jobs Scheduled jobs will display jobs that you have scheduled yourself. You will see other jobs scheduled for internal tasks within PowerShell Universal. ## Jobs You can use the Jobs tab to view jobs that are running, have executed or have failed. Jobs should typically not be marked as failed within Hangfire. This is a sign of an internal error within PowerShell Universal. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devolutions.net/powershell-universal/development/hangfire.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.