Datplan help

Troubleshoot from the run evidence, not by repeating the same pull

Work through connection, allowance, endpoint, local-file and reporting checks in order. Preserve the evidence before changing the workflow.

Safe diagnostic order

Find which stage failed

  1. Confirm selectionCheck the workspace, source, provider organisation or portal, and any reporting window.
  2. Check authorisationUse Test connection where available and reconnect only through the provider’s consent flow.
  3. Check plan and provider limitsReview pull credits, data allowance, provider quota and access permissions.
  4. Read endpoint and run messagesDistinguish complete, empty, skipped, partial, cancelled and failed results.
  5. Check the local outputVerify timestamps, folder availability, file names and that the downstream report reads the intended folder.
  6. Check the modelVerify grain, aggregation, filters and relationships before treating an unexpected total as a sync failure.
  7. Export safe diagnosticsUse the app’s report or diagnostic ZIP and inspect it before sending anything to support.

Useful support information

  • Datplan app version
  • Source name and general connection context
  • Date and time of the affected run
  • Overall and endpoint status
  • Exact non-sensitive error message
  • Sanitised screenshot or diagnostic report

Do not send

  • Passwords or provider tokens
  • Authorisation codes or secrets
  • Full local databases
  • Raw financial or customer records
  • Sensitive screenshots
  • Private file paths when unnecessary

Troubleshooting questions

Common first checks

A provider connection is missing. What should I do?

Confirm the selected workspace and source, check that the provider account still grants access, then reconnect through the provider consent flow. Do not send tokens or authorisation codes to support.

A sync completed with no rows. Is that a success?

Not necessarily. Check the selected tenant, date or discovery window, endpoint result, source permissions and whether the source legitimately contains no eligible records.

A scheduled job did not run. What should I check?

Check the Datplan execution history, source access, plan allowance, Windows Task Scheduler or app-open mode, PC sleep state, network, export folder and provider status.

My dashboard total looks too high. What is the first check?

Check the row grain and any relationships. A many-to-many join or a measure repeated across invoice lines, activities or bridge rows can multiply totals.

See Datplan with real reporting data—without connecting a live account

The Windows app is free to download and includes Datplan Demo data, so you can test sync, dashboards, reporting grains and exports first.