> 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/da/udvikling/hangfire.md).

# Hangfire

Vis dashboardet for Hangfire-jobudførelse i PowerShell Universal for at diagnosticere planlagte jobs, kørende jobs og fejl, der påvirker udførelsen af automatisering.

[Hangfire](https://www.hangfire.io/) er det planlægningsbibliotek, som PowerShell Universal bruger til at udføre og planlægge job. Det kan være nyttigt at se status for Hangfire-køerne til jobudførelse. Dette er typisk nyttigt, hvis De har job, der ikke kører, eller tidsplaner, der ikke starter på de rette tidspunkter.

De kan få adgang til Job Details-dashboardet ved at klikke på knappen Diagnostics i **Run > Jobs**.

## Planlagte jobs

Planlagte jobs viser jobs, som De selv har planlagt. De vil se andre jobs, der er planlagt til interne opgaver i PowerShell Universal.

## Jobs

De kan bruge fanen Jobs til at få vist jobs, der kører, er blevet udført eller er mislykkedes. Jobs bør typisk ikke markeres som mislykkede i Hangfire. Det er et tegn på en intern fejl i 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/da/udvikling/hangfire.md?ask=<question>&goal=<user_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.