Support
If something about the connector between Clockify and Microsoft Dynamics 365 Business Central is not behaving as you expect, write to support@spainlink.es. You can expect a first reply within one business day.
Check inside Business Central first
Most problems explain themselves where they happened, so a quick look in your Business Central often answers the question faster than a ticket:
- The Clockify Time Entries list shows every entry the connector received, and a failed entry carries its own error message on the row. The message states the reason, for example a posting date outside the allowed range or a missing mapping.
- The Clockify Sync Log records every action the connector took, with timestamps. Opening it from a selected entry shows that entry’s full history.
Posting failures are never silent. A failed entry stays visible in the list with its reason until it is resolved. Nothing is dropped, and nothing disappears.
What to include in a report
The more of this you send, the more useful the first reply will be:
| Include | Why it helps |
|---|---|
| Your company name | Identifies your environment and configuration |
| The approximate time it happened | Lets us find the matching activity in the logs |
| The Clockify entry id, if you have one | Takes us straight to the exact entry |
| What you expected to happen | Separates a defect from a configuration question |
| A screenshot of the entries list row, or its error message | Shows us exactly what you are seeing |
Never include passwords, API keys or client secrets in a support message. We will never ask for them by email.
Related pages
- How it works explains the sync flow and the guarantees behind it.
- The mapping model covers what happens when a person or project has no mapping yet.
- Getting connected walks through setup, which resolves most first-week questions.
- Frequently asked questions answers the questions we hear most often.