The count of Finance & Operations batch jobs sitting in Error status over the last 24 hours, a common F&O failure mode that is easy to miss.
At a glance
The number of Finance & Operations batch jobs that ended in Error status in the last 24 hours: Data Management / DIXF import-export jobs, recurring integration jobs, and posting jobs. F&O runs a great deal of work on the batch framework, and a failed batch job sits quietly in the queue with no email and no banner. This card makes that silent failure visible. A non-zero count, especially one left unresolved beyond a day, means scheduled processing has stalled.
| What it counts | F&O batch jobs in Error status over the trailing 24 hours. Conceptually count(batch jobs WHERE status = Error) across the in-scope job types: Data Management / DIXF import and export projects, recurring integration jobs, and posting / processing jobs. Each errored job is counted once until it is resolved or re-run. |
| Which jobs | The batch framework runs both system housekeeping and business processing. The card focuses on the jobs that move money and data: data import / export, recurring integrations feeding or draining the ecom bridge, and posting jobs (invoicing, ledger, inventory recalculation). |
| What “Error” means | A batch job whose run ended in the Error state, distinct from Executing, Waiting, or Ended (success). A job that errored on one occurrence but later succeeded on a retry does not stay counted. A job that errored and was never re-run stays in the queue. |
| Multi-Company / legal entity | F&O batch jobs run within an environment and can touch multiple legal entities. The card is environment-level, because a stuck batch server or a failing recurring job affects every entity it serves. |
| Time window | 24H (rolling 24-hour error window) |
| Alert trigger | >0 unresolved >24h. Any batch job that has been in Error for more than 24 hours raises an alert. A fresh error may self-resolve on the next scheduled occurrence; an error left unresolved beyond a day means nobody is watching the queue. |
| Roles | owner, finance, engineering |
Calculation
Calculated automatically from your Microsoft Dynamics 365 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A brand runs Finance & Operations with a set of scheduled batch jobs feeding invoicing, integrations, and inventory costing. The card is read 23 Mar 26 over the prior 24 hours.| Batch job | Type | Status | Age in error |
|---|---|---|---|
| Recurring import: storefront orders | Data Management / DIXF | Error | 26h |
| Sales invoice posting (batch) | Posting | Error | 3h |
| Inventory recalculation | Processing | Ended (success) | n/a |
| Export: customer master to CRM | Data Management / DIXF | Error | 31h |
| Vendor payment proposal | Processing | Ended (success) | n/a |
| Batch Job Error Queue (this card) | 3 in error | 2 over 24h |
- Three jobs are in Error, and two have been stuck for more than 24 hours. That is what trips the alert: the rule is >0 unresolved past 24h, and the import (26h) and the export (31h) both qualify. The sales-invoice posting error is only 3 hours old and may clear on its next occurrence, but it is worth watching.
- The stuck storefront-orders import is the dangerous one. A DIXF import that brings storefront orders into F&O has been failing for over a day. That means a day of orders may not have become sales orders or invoices, which surfaces downstream on Ecom Orders Missing Matching D365 Free-Text Invoice.
- The sales-invoice posting error blocks revenue recognition. While that posting job is in Error, invoices are not posting to the ledger, so booked revenue lags. If it persists it will show on the finance-health cards and delay the period roll-up.
- A clean count is the goal, not just below an arbitrary number. Unlike a volume gauge, the healthy reading here is effectively zero unresolved errors. Any job left in Error past a day is a process gap. Pair this with D365 Finance Health Score, which folds batch-queue health into the overall finance-ops grade.
Sibling cards merchants should reference together
This card is the F&O processing-health signal. Pair it with the cards that show what stalled processing breaks.| Card | Why pair it with Batch Job Error Queue |
|---|---|
| Power Automate Flow Failures (ecom integration) | The cloud-flow sibling. Power Automate is the integration layer; batch jobs are the in-ERP processing layer. Integration problems often show on both at once. |
| Open / Not-Posted Journal Entries | A failed posting batch leaves journals unposted. This card and that one move together when the posting queue stalls. |
| Journal Imbalances Rejected at Posting | A common reason a posting batch errors: an out-of-balance journal the framework refuses to post. |
| D365 Finance Health Score | The composite grade. Batch-queue health is one of its inputs, so a rising error queue pulls the score down. |
| Ecom Orders Missing Matching D365 Free-Text Invoice | The commerce consequence. A stuck order-import or invoice-posting batch leaves storefront orders with no matching invoice in F&O. |
Reconciling against Microsoft Dynamics 365
Where to look in Business Central / Finance & Operations: The closest native equivalents in the Dynamics UI are:F&O > System administration > Inquiries > Batch jobs (the authoritative batch queue with status per job) F&O > System administration > Inquiries > Batch job history (run history and error detail per occurrence) F&O > Data management > Data project execution history (DIXF import / export run status and staging errors) Business Central > Job Queue Entries (the BC equivalent, where Status = Error flags failed scheduled tasks)To verify the count, open Batch jobs in F&O and filter to status Error; the number of in-scope jobs should match this card. Open each errored job’s history to see the failing class and the error message (a staging validation failure, a locked record, a closed period, an out-of-balance journal, or a connector timeout). In Business Central the equivalent is the Job Queue Entries list filtered to Error. Common mistakes when comparing by hand:
- Including system housekeeping jobs. The batch framework runs many internal maintenance jobs. This card focuses on data, integration, and posting jobs, so an unfiltered queue view can read higher.
- Counting historical occurrences instead of current state. Batch job history shows every past error including ones already resolved. The card counts jobs currently in Error, not the lifetime error count.
- Missing the >24h dimension. The alert fires on errors unresolved past 24 hours. A queue glance that does not check the error age will not match the alert logic.
| Reason | Direction | Why |
|---|---|---|
| Job-type scope | Card lower | The card counts data, integration, and posting jobs. The native queue includes system housekeeping jobs, so an unfiltered view reads higher. |
| Current state vs history | Card lower | The card counts jobs currently in Error. Batch job history accumulates every past error including resolved ones, so the history list is longer. |
| Self-recovering recurring jobs | Card lower | A recurring job that errored on one occurrence but succeeded on the next is no longer in Error. The card reflects current status. |
| 24-hour window edge | Either | The rolling 24-hour window captures a different slice near the boundary than a fixed clock-day filter in the UI. |
| Environment scope | Either | The card is environment-level. If you check the queue in only one legal entity’s context you may miss errors on jobs that serve another entity in the same environment. |