Skip to main content
Troubleshooting

Find a fix

Search for what you're seeing, or browse by area. Each symptom links straight to the page that explains the cause and the fix.

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.
A user forgot their password
Forms users can self-reset. Windows / Entra ID users go through their network admin.
I changed a role but the user still has the old permissions
They need to log out and back in. Roles are evaluated at login.
New translations don't appear in the planning view
Translations are cached in the browser. A hard refresh (Ctrl+F5) clears the cache.
The map doesn't load
Likely missing or wrong PTV map token / URI in the application setup.
Chrome won't open dynamicsnav:// or bc:// links
Known Chromium issue. Workaround: edit the Preferences file to whitelist the protocol.
Browser blocks file:// links to documents on a share
Browser security blocks navigating across security boundaries. Use a local file extension or a different scheme.
Browser won't ask for the user's location
Location prompt is disabled in browser site settings. Enable it per browser.
Exchange: "Invalid client" or AADSTS700016
Wrong Client ID, Tenant ID, or expired Client Secret in the Azure app registration.
Exchange: "Insufficient privileges" or consent required
API permissions are set but admin consent was never granted in Azure AD.
Zapier won't authenticate
API key is wrong, scoped incorrectly, or the Dime.Scheduler URL is malformed.
A Zap doesn't trigger
Trigger conditions or filters are too narrow, or the polling interval hasn't fired yet.
Component is blank or layout looks broken
Profile or layout misconfiguration, or stale browser cache.
NAV web service calls fail
NAV web services not published, wrong tenant, or company name mismatch.

First steps for any issue

If your symptom isn't listed above, run through these in order. They resolve a large share of incidents on their own.

  1. 1
    Check the transactions log
    Most integration problems show up here first. Open errors and read the latest failure message.
  2. 2
    Verify connectivity
    Confirm the back-office system is online and that firewalls allow traffic from Dime.Scheduler to it. 504 / timeout errors almost always come from here.
  3. 3
    Re-check authentication
    Credentials, secrets and API keys expire. Make sure the configured account hasn't rotated, locked, or lost the required permissions.
  4. 4
    Hard-refresh & re-login
    For UI oddities and stale data: Ctrl+F5, try an incognito window, and log out and back in to pick up role and translation changes.

Browse by area

Still stuck?

Gather the error message, a screenshot, the exact steps to reproduce, and the time it started. For urgent issues affecting production systems, contact support directly with that diagnostic information ready.

Contact support