Job Queue & Core BC BC Job Queue Entry / Task Scheduler (background session) or API/OData call Microsoft Learn: Task scheduler (AL methods that throw nonretriable exceptions in background sessions); microsoft/AL issue #5547; microsoft/ALAppExtensions issue #9801

Job Queue Entry Fails: Client Callbacks Are Not Supported (Confirm or Dialog in a Background Session)

Raw System Error String
Microsoft Dynamics 365 Business Central Server attempted to issue a client callback to show a confirmation dialog box: ... Client callbacks are not supported on Microsoft Dynamics 365 Business Central Server.

What It Means

A job that works when a user runs it by hand fails when the job queue runs it. Typical cases: posting or releasing orders, an order import, or a report or export. The Job Queue Entry goes to Error and Show Error gives this text. Through an API or OData call the text says 'Business Central Data Services' instead of 'Server'.

Root Cause

Job queue entries run in a background session with no user interface. Microsoft's task scheduler docs state that Confirm, StrMenu, Page.RunModal, Report.RunModal, File.Download and similar UI calls are not allowed there. A Confirm gives 'attempted to issue a client callback to show a confirmation dialog box'; a file download gives '...a client callback to download a file'. The exception is not retriable, so the job fails at once. The dialog usually comes from an extension or from base-app code that does not check GuiAllowed() (for example, ALAppExtensions issue #9801: a VAT registration confirm in codeunit 249 called from the Customer API).

Step-by-Step Fix

  1. Open Job Queue Entries, select the failed entry and choose Show Error. Copy the text after the colon: it names the dialog and often the object, for example '(CodeUnit 249 VAT Registration Log Mgt.)'.
  2. If the text names an extension's object, contact that publisher. Ask them to wrap the dialog in 'if GuiAllowed() then' or skip it in background sessions.
  3. If it names a Microsoft object, check for a newer Business Central update and open a support request if none fixes it.
  4. Short-term: change the setup that triggers the question (for example, turn off the option that asks for confirmation), or run the job once with Run once (foreground) to clear the backlog.
  5. For file downloads in a job, change the job to save the file to a supported target (for example, attach it to a record or send by email) instead of downloading it.
  6. Set the entry back to Ready (Restart) after the fix.

Verification Steps

How to verify: The job queue entry runs on schedule and ends with status Ready (recurring) or Finished, and Show Error has no new entry.

Sources & References

Early Access · 30-Day Sandbox Pilot

Stop Order Sync Failures Before Customers Notice

The Order Flow Doctor monitors Microsoft Dynamics 365 Business Central order flows across Shopify, EDI (TrueCommerce, SPS), 3PLs, and carriers. Get automated root-cause diagnosis and one-click fixes.

We respect your privacy. No spam. You will only be contacted when pilot slots open for your stack.