Skip to content

Document Dispatch

Multimail of Documents result in BC-Sided-Error

Fixed - Extension Delivery planned

Description: When attempting to send multiple records through Document Dispatch with the output type "E-Mail," the entries are set to error, and a message is displayed indicating that the application has exceeded its IncomingBytes limit. This issue is triggered when more than 150 MB of data is uploaded within a 5-minute period per mailbox, causing throttling on the specific App ID and Mailbox combination.

Impact: Users are unable to send multiple records via email through Document Dispatch when the data exceeds the specified limit within the given time frame, resulting in incomplete dispatch entries and operational delays.

Created: January 28, 2026
Priority: High

Automatic Reminder Email Dispatch Fails While Manual Direct Dispatch Works

Fix Planned

Description:
In Business Central 2025 Wave 2 (v27), automatic dispatch of reminder documents via Document Dispatch (Version 27.1.3.0, CORE 27.5.0.0) may create both a Dynamic Recipient and an Extended Recipient entry, even though only Dynamic Recipients are configured. The Extended Recipient entry fails because no Extended Recipient is defined, causing the automatic reminder email dispatch to fail. Manual direct dispatch of the same reminder works as expected. The behavior appears to be related to the recipient priority merge functionality, where the merged priority configuration may not be refreshed correctly after an extension update, leading to different recipient evaluation between automatic and manual dispatch.

Impact:
Customers using automatic reminder email dispatch with dynamic Business Partner assignment and reminder-specific dispatch profiles may experience failed automatic reminder delivery due to incorrectly created Extended Recipient entries. This can result in inconsistent behavior between automatic and manual dispatch and may require manual intervention to ensure reminders are sent successfully.

Created: July 21, 2026
Priority: Medium

Job Queue processing does not start for Await entries

In Process

Description: When a Dispatch Profile is configured with “Automatic sending when posting” and “Process via Job Queue” enabled, posting a Sales Invoice correctly creates an Await entry, but the Job Queue does not process this entry. This occurs regardless of whether a Dispatch Schedule is configured, disabled, or deleted.

Impact: Sales Invoices that rely on automatic dispatch processing remain in Await status and are not sent as expected, requiring manual intervention or alternative processing and potentially delaying document delivery.

Created: September 4, 2026
Priority: Low

Duplicate "New" Action and Incorrect Multi-Select Actions in Dispatch Schedule

In Process

Description: When logged in as a Document Dispatch Admin and opening the Dispatch Schedule, two “New” actions are displayed instead of a single intended option. In addition, the “Multi-Select” and “Reset Processing Window” actions are visible and available even though they are not intended for use in non–multi-selection scenarios.

Impact: Users may experience confusion and inconsistent behavior when managing dispatch schedules, as unintended actions are presented and potentially used in contexts where multi-selection is not supported.

Created: September 7, 2026
Priority: Low