> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-logs/runbook-job-details.md). # Runbook Job Details View RealmJoin runbook job metadata, real-time console output, and details from Azure Automation jobs. ## Overview RealmJoin Portal allows you to view runbooks jobs from Azure Automation.

On the left side of the page you will find metadata about the runbook job, its type/context, job ID and its caller. Be aware, "caller" is only present when runbooks are RealmJoin-aware and report this information, as Azure Automation has no concept for this. On the right, you will find multiple tabs, representing: ### Console This will show a live feed of the runbooks output. In contrast to Azure Automation, output of a runbook is readable in real time. If the job emitted tables, the console shows them in a compressed form by default, so that status lines stay readable. Use "Show full output" to switch to the complete, untruncated text and "Show compressed tables" to switch back. Using "Copy to Clipboard" you can copy the full output to use it e.g. in a service/ITIL ticket system. This always copies the full output, regardless of which view is shown. ### Output Data This renders the objects the runbook emitted as sortable, filterable tables, so that long values such as GUIDs stay fully readable instead of being truncated by the PowerShell console formatter. Each table can be exported to Excel or CSV. Output Data is available for live runs only — for archived jobs, use the **Console** tab. See [Runbook Output Data](/dev-reference/runbook-output-data.md) for how to work with the tables, and for what a runbook has to do so that its results show up here. ### Input Review the parameters used to start the runbook job.

### Errors and Warnings If present, warnings and errors which are not part of regular output will be shown in these two tabs.

### Exceptions If the PowerShell script of the runbook threw an exception (and the runbook thus failed), you can review the Exception here. Exceptions will also be shown above the regular output in **Console** if present to simplify identifying problems.

### Source This allows you to review the runbooks source code associated with this job.

--- # 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.realmjoin.com/automation/runbooks/runbook-logs/runbook-job-details.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.