More Control Over Integrations with the New DataHub Error Log

Integrations are the backbone of modern logistics operations. Orders, inventory updates, transport statuses, and customer information continuously move between systems. But when something goes wrong within an integration flow, the same challenge often appears: error messages disappear into technical logs, isolated notifications, or complex monitoring screens. As a result, identifying, prioritizing, and resolving disruptions takes unnecessary time.

With the new DataHub Error Log in the Boltrics solution, that changes. Not by adding even more technical information, but by making errors operationally manageable. One central location where you immediately see which integrations require attention, which notifications are critical, and which are simply noise.

This aligns with Boltrics’ vision on logistics software: simplifying processes, centralizing control, and enabling logistics service providers to operate faster and smarter.

From Isolated Error Messages to Centralized Insight

The new DataHub Error Log makes integration issues directly visible through a clear tile on the Boltrics home screen. Instead of searching through technical logging or separate flow runs, you instantly gain insight into open notifications across all DataHub integrations.

From the tile, users can directly open the DataHub Error List. Here, error messages are automatically grouped based on:

• the error message itself
• the moment the notification occurred
• the frequency of recurring errors

This means you no longer only see that something is going wrong, but also how structural the issue actually is.

And that is exactly where the difference between operational noise and real disruptions becomes clear.

Not Every Error Is Critical

Temporary disruptions are common in logistics IT environments. Think of a short timeout towards an FTP server or an external API responding slower than expected. If the flow continues successfully afterward, this does not necessarily create an operational issue.

However, when the same error message appears five times or more within a single hour, the situation changes. That is when action is required before processes are disrupted or customers experience impact.

That is why the DataHub Error Log works with Error Rules. These rules automatically determine how notifications are classified:

• known, harmless notifications → Low
• recurring disruptions → High or Critical
• unknown errors → default Medium

The list uses color coding to make critical errors immediately visible. In addition, the severity of a grouped notification is automatically determined by the highest severity level within the underlying errors.

The result: less distraction. More focus on what truly impacts your operation.

From Notification to Resolution. Directly Within the Same Environment

The strength of the DataHub Error Log is not only in monitoring, but especially in direct follow-up.

From every error notification, users can immediately navigate to the correct DataHub Flow Run. There, they can inspect the transaction, analyze exactly where the flow failed, and restart the integration if required.

Additionally, every notification can be assigned a status, such as:

• Restarted
• Resolved
• No Action Required
• To Investigate

This transforms error handling from an individual or ad hoc activity into a transparent operational process for the entire team. Everyone immediately sees which notifications are still open and which have already been handled.

How Does It Work Technically?

The technical setup of the DataHub Error Log is intentionally kept simple:

1. A notification occurs within a DataHub Flow.
2. Business Central automatically retrieves the notifications through a job queue.
3. The notification is stored in the DataHub Error Log.
4. The Error Rule Evaluator automatically determines the correct severity.
5. The error appears grouped within the DataHub Error List.

By default, the Error List only shows notifications with the status New, allowing users to focus directly on unresolved issues. Filters can of course be adjusted to also display previously investigated or resolved notifications.

More Control Over Integrations. Without Additional Complexity.

For logistics service providers, integration management is not about technical dashboards. It is about operational control. Detecting issues faster. Prioritizing more effectively. And resolving disruptions before they impact customers or processes.

The new DataHub Error Log brings exactly that together in one central environment:

• Monitor: All DataHub errors centrally visible
• Classify: Automatic severity assignment through Error Rules
• Resolve: Directly inspect, restart, and follow up

Not just another logbook. But an operational dashboard for modern integration control.

From Error Notification to Operational Control

The number of integrations within logistics operations continues to grow. And with that growth comes the increasing need to manage errors operationally instead of merely registering them technically. With the DataHub Error Log, you gain one central environment to monitor notifications, classify them intelligently, and resolve them directly. Without adding extra complexity to your operation.

Would you like to see how this works in practice? Visit the Learn page about the new DataHub Error Log and discover how to gain faster control over your integrations and error handling within the Boltrics solution.