Monitoring Hub

Long-running BI Pixie operations — Add Pixies runs, batch report updates, bulk Pixie removals — surface in Microsoft Fabric's Monitoring Hub alongside other Fabric jobs. This page describes how to find BI Pixie jobs, what each status means, how to inspect a job's details, and how to retry a failed job.

What Shows Up in the Monitoring Hub

Any BI Pixie operation that takes more than a few seconds is registered as a Fabric job. That includes:

• Add Pixies — adding Pixies to one or more reports.
• Update Pixies — refreshing existing Pixies after settings change.
• Remove Pixies — cleaning Pixies from reports.
• Batch operations — running Add or Update across many reports at once from the Managed Reports view.
• Dashboard install — provisioning the BI Pixie Dashboard semantic model and report.

Short, synchronous actions (saving a setting, viewing recent events) do not register as jobs.

Find BI Pixie Jobs

1. In the Fabric portal left navigation, click Monitor to open the Monitoring Hub.
2. Use the Item type filter and select BI Pixie. The list narrows to BI Pixie jobs only.
3. Combine filters to drill in further:
   • Workspace — limit to one workspace.
   • Status — for example, only failed jobs.
   • Submitted by — only jobs you started.
   • Time range — last hour, day, week.

Job Statuses

Every BI Pixie job moves through a small set of statuses. Hover any status pill in the Monitoring Hub for the same definitions.

• Not started. The job has been accepted and is waiting for a worker to pick it up. Typical wait is a few seconds; under heavy tenant load it can be longer.
• In progress. A worker is actively processing the job. For batch operations, the progress bar shows reports completed out of the total.
• Succeeded. The job finished and every report in scope was processed without error.
• Failed. The job did not complete. The underlying error is recorded in the job details. For batch operations, individual reports that could not be processed are listed in the per-report results — other reports in the same batch may have completed successfully and remain usable.
• Cancelled. You — or another workspace member — cancelled the job before it finished. Cancellation is best-effort; reports already in flight when you cancel may still complete.

These names match the standard Fabric job statuses. The Monitoring Hub may render In progress as Running and Not started as Queued in some places. The underlying state is the same.

Inspect a Job

Click any row in the Monitoring Hub to open its details pane.

• Summary — operation name, item, workspace, submitted-by user, start and end time, duration.
• Per-report results — for batch operations, a table listing each report's status, the version of Pixies applied, and any error message. Failed rows have a Copy error link that captures a redacted error you can share with support.
• Activity log — timestamped log of milestones (queued, started, fetched report, applied Pixies, saved back to the workspace, finished).
• Related events — link into the BI Pixie item's Events tab pre-filtered to the time window of the job, so you can confirm telemetry started flowing after a successful run.

Retry a Job

Failed jobs can be retried directly from the Monitoring Hub.

1. Open the job's details pane.
2. Click Retry in the action bar.
3. For batch operations where some reports completed and others did not, retry processes only the reports that previously failed. Reports that already succeeded are not touched.
4. For jobs where no reports completed, retry replays the entire operation. If the failure was transient (a Power BI transient error, a token refresh window) the retry usually succeeds without changes.

For repeated failures, open the related report in Power BI directly and verify you have Build permission on its underlying semantic model. Most reproducible failures trace back to permission gaps that the original submitter had at run time.

Cancelling a Running Job

If you started a large batch by mistake, click Cancel in the details pane. Reports already in flight may still complete. Reports not yet started will be skipped, and the final status will be Cancelled. Any reports that did complete keep their Pixies — cancellation does not roll back successful work.

Notifications

When you submit a job, the BI Pixie item shows a Fabric toast notification on completion. If you navigate away from the BI Pixie item, the Monitoring Hub remains the source of truth — open it any time to check on jobs you started.

What's Next

• Managed Reports — verify a job by running Check for events on a freshly tracked report.
• Add Pixies to Your Reports — start a new Add Pixies job from the sidebar.
• FAQ — answers to common questions about jobs, throughput, and limits.