API’et, som sender data til Business Central, er nu oppe igen med nye forbedringer og optimeringer. Vi overvåger fortsat løsningen tæt for at sikre stabil drift.
----------------------------------
The API responsible for sending data to Business Central is now back online with new improvements and optimizations. We continue to monitor the solution closely to ensure stable operations.
Posted Feb 27, 2026 - 09:41 CET
Identified
DK: Synkroniserings-API’et er desværre ustabilt igen og er derfor midlertidigt taget ned. Timeregistrering fungerer fortsat som normalt. Timer vil dog ikke blive sendt til ERP, mens vi arbejder på at løse problemet. Vi beklager generne og opdaterer løbende.
ENG: The synchronization API is unfortunately unstable again and has been temporarily taken offline. Time registration is still working as normal. However, hours will not be sent to the ERP system while we are resolving the issue. We apologize for the inconvenience and will provide ongoing updates.
Posted Feb 27, 2026 - 09:35 CET
Monitoring
DK: Der er tilføjet et fix til API’et, så det igen kører stabilt. Synkroniserings-API’et er nu oppe igen, og vi afmelder hændelsen, men fortsætter med at overvåge for eventuelle nye uhensigtsmæssigheder.
ENG: A fix has been implemented in the API, and it is now running stably again. The synchronization API is back online, and we are closing the incident while continuing to monitor for any further irregularities.
Posted Feb 26, 2026 - 15:27 CET
Investigating
DK: Problemet med synkroniserings-API’et er desværre opstået igen. API’et er taget ned for yderligere undersøgelser.
Al synkronisering er midlertidigt stoppet i begge retninger. Det betyder, at: - Timer registreret i 365Tid ikke bliver sendt til Business Central. - Stamdata og øvrige opdateringer fra Business Central ikke bliver overført til 365Tid.
Timeregistrering kan fortsætte som normalt i 365Tid, men der vil ikke ske nogen dataudveksling mellem systemerne, så længe API’et er lukket.
Vi arbejder på at identificere årsagen og opdaterer løbende, så snart der er nyt.
ENG: The issue with the synchronization API has unfortunately occurred again. The API has been taken offline for further investigation.
All synchronization has been temporarily stopped in both directions. This means that: - Hours registered in 365Tid will not be sent to Business Central. - Master data and other updates from Business Central will not be transferred to 365Tid.
Time registration can continue as normal in 365Tid, but no data exchange between the systems will take place while the API remains offline.
We are working to identify the root cause and will provide continuous updates as soon as more information becomes available.
Posted Feb 26, 2026 - 12:49 CET
This incident affected: 365Tid (365Tid.dk, 365tid App, 365Tid API).