Following the successful May release, the next set of changes is now available in production.
What is new
This release focuses on diagnostics. To improve troubleshooting, we analyzed millions of transactions and identified a set of status codes generated by back-office systems such as Business Central, Exchange, and the generic webhook connector.
When these systems return an unexpected response, our connectors analyze it and try to classify the issue. Each transaction is tagged with a code that you can match against the list of known errors in our documentation and use to find a suggested solution:
We also made several improvements to the MCP server. In addition to refining MCP capability metadata, we introduced a tenant-wide default time zone that is used when the MCP consumer does not specify one.
What's next
Additional releases are scheduled for July and August. The main feature, which continues the diagnostics theme of this release, is a centralized outbound queue in the new Business Central connector - a single, observable pipeline for sending data from Business Central to Dime.Scheduler.
