Troubleshooting

The most common questions about the two-way message flow between Dime.Scheduler and Business Central, grouped by what you're seeing.

Find your symptom

Appointments don't show up in Business Central

Usually a missing or invalid connector, or BC is unreachable from Dime.Scheduler.

Appointment in BC is stuck on "Error"

Dime.Scheduler delivered it, but BC couldn't process it. Check the Dime.Scheduler Appointments table in BC.

Request channel timed out

Firewall is blocking traffic from Dime.Scheduler to BC, or the request is too slow.

HTTP Request Unauthorized

Wrong credentials, expired secret, or missing API permissions on the BC side.

BC complains about time synchronization

Server clocks are drifting. Token validation fails when clocks are off by more than a few minutes.

Business Central to Dime.Scheduler

The first thing you do on a new Dime.Scheduler instance is run the FastTrack Wizard in Business Central. Work through every step carefully.

The first step is also the most common place to get stuck: it's where you set up the flow to Dime.Scheduler, with the environment and the credentials to authenticate against it.

Watch out for these:

• User/password authentication
  • An account used in more than one tenant.
  • A real person's account instead of a service account. The day that person resets their password, the integration breaks. Use a service account like [email protected].
  • Don't use any domain managed by Dime Software, either: that's a security risk.
  • It must be a Forms account on a domain your customer controls. MS Entra ID accounts aren't supported by the API.
• Environment (sandboxSandboxThe separate Dime.Scheduler environment where upcoming features arrive before the production release. It has its own API host, sandbox.api.dimescheduler.com, so API clients target it explicitly. or production): the on-prem option refers to Dime.Scheduler on-prem, not BC on-prem.

Dime.Scheduler to Business Central

The flow from BC to Dime.Scheduler is easy to set up, thanks to the FastTrack WizardFastTrack wizardThe setup wizard inside Business Central or NAV that connects it to Dime.Scheduler and switches on the modules to plan from. It writes the source app and creates the source types for each enabled module. and the connectorConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out.. The return flow is trickier, because it depends on how that particular BC is set up. Two things can fail: Dime.Scheduler can't reach BC, or BC receives the appointmentAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board. but can't process it.

Appointments don't show up in Business Central

Start at the transactions. Open them from the sidebar, or right-click the appointment on the planning boardPlanning boardThe main graphical scheduling surface where dispatchers drag tasks onto resources across a timeline. and choose View transactions.

That opens the appointment's detail page: basic info, the associated connector (if any), and every transactionTransactionThe recorded call Dime.Scheduler makes to a connected system when the planning changes. It counts as successful on an HTTP 200, which means the endpoint received it, not that the back office processed it. that tried to write back to Business Central, Exchange, or a webhookWebhookThe generic connector that POSTs every appointment change as JSON to a URL you choose. It delivers the message and leaves interpretation to the receiving system..

The transactions usually tell you exactly what went wrong. Common causes:

• No connector for this item. Data sent from BC carries a Source AppSource appAn identifier Dime.Scheduler attaches to data so it can route a change back to the correct back-office system. identifier. To send a planned appointment back, Dime.Scheduler looks for a connector with the same Source App. No match, nothing sent.
• Invalid or incomplete connector. Usually the wrong URL or credentials (or app registration details, for BC cloud).
• Back-office unavailable: the administrators need to make the BC SOAP URL reachable from Dime.Scheduler.

Appointments couldn't be processed in Business Central

When Dime.Scheduler drops the appointment into BC, the transaction is marked successful on the Dime.Scheduler side. That doesn't guarantee BC processed it.

In Business Central, open the Dime.Scheduler AppointmentsStaging tableThe Dime.Scheduler Appointments table in Business Central where incoming appointments land first. Business Central processes rows from there, so a row can be received and still fail processing. table. It lists the transactions and their status. Anything not marked Processed went wrong: click the status column for details.

Processed means the planning data went through as expected. Error means it didn't, and the Error Message column tells you exactly why.

Time zone mismatch

Appointments scheduled in Dime.Scheduler show incorrect times in Business Central (e.g. 9 AM in Dime.Scheduler appears as 7 AM in BC).

Applies to: Business Central SaaS.

Cause

A time zone mismatch between Dime.Scheduler and Business Central, usually a fixed shift (2 hours is common), almost always from an incorrect time zone in the connector setup. There's no error code for this: the appointment is delivered fine, just at the wrong time, so it's a configuration quirk rather than an exception.

Fix

Open the Dime.Scheduler SetupDS SetupThe connector’s setup page in the back office (DS Setup in NAV, DS Connector Setup in Business Central). It holds the same settings as the FastTrack wizard, plus actions to send data manually. page in Business Central and set the Time Zone field:

The same field also appears at the bottom of the FastTrack wizard:

Transaction errors

Every failed transaction is tagged with a stable code (e.g. [DSBC003]). See Transaction Errors for the full reference and partner-facing fixes.

A recipe uses this page

• Diagnose a failed Business Central syncFind the failing transaction, read the error, and apply the right fix.