TachoSync Integrations: Difference between revisions
upload frequency, retry logic, maximum retry duration, naming conventions for uploaded files, was added |
|||
| Line 89: | Line 89: | ||
If issues persist, collect the “Last Event” details from the Integrations page and contact Support. | If issues persist, collect the “Last Event” details from the Integrations page and contact Support. | ||
=== Upload Frequency === | |||
TachoSync sends files to your SFTP server '''as soon as they become available'''. | |||
* When a new tachograph file is downloaded from the vehicle or driver card, it is immediately added to the SFTP sync queue. | |||
* Sync happens '''continuously''', not on a fixed schedule. | |||
* If you enable “Include historical files,” TachoSync also adds your previously downloaded files to the queue and syncs them in batches based on current system load. | |||
'''What this means for you:''' | |||
There is no need to manually trigger a daily or hourly sync. Files are pushed automatically as soon as they are downloaded or discovered. | |||
---- | |||
=== Retry Logic === | |||
If TachoSync cannot deliver a file to your SFTP server, it will attempt to retry depending on the type of error. | |||
==== We do NOT retry when the issue is permanent: ==== | |||
* Incorrect username or password | |||
* Insufficient permissions on the SFTP destination (cannot create directories or upload files) | |||
* Invalid upload path | |||
These issues require you to fix the configuration and then retry manually (using the “Retry failed files” feature (''soon to be added''). | |||
==== We DO retry when the issue may be temporary: ==== | |||
Examples of temporary problems: | |||
* The SFTP server is unreachable | |||
* Connection timeouts | |||
* Network interruptions | |||
==== Retry pattern ==== | |||
TachoSync uses an '''exponential backoff''' strategy for temporary errors, with up to '''5 retry attempts''': | |||
# After 3 seconds | |||
# After 9 seconds | |||
# After 27 seconds | |||
# After 1 minute 21 seconds | |||
# Final attempt (~4 minutes after the initial failure) | |||
If all retry attempts fail, the file is marked as '''failed''', and no further automatic attempts are made. | |||
---- | |||
=== Maximum Retry Duration === | |||
The entire retry cycle lasts approximately '''4–5 minutes''' from the first failed attempt. | |||
After that: | |||
* The file is '''not retried automatically''' | |||
* It will remain marked as '''failed''' until you fix the underlying issue and manually trigger the sync again | |||
This prevents infinite retry loops and reduces unnecessary load on both systems. | |||
---- | |||
=== Naming Conventions for Uploaded Files === | |||
TachoSync '''does not rename''' your files. | |||
The filename that appears in your SFTP server is '''exactly the same''' as the file stored in TachoSync. | |||
The only exception is the '''file extension''', which depends on the format you selected when configuring the integration: | |||
* <code>.DDD</code> | |||
* <code>.TGD</code> | |||
* <code>.V1B</code> or <code>.C1B</code> | |||
Folder structure is based on your integration settings (company hierarchy, vehicle folder naming, driver folder naming). | |||
'''Example path:''' | |||
<code>/North Division/North Logistics/356710123456789/2024-09-10_123456.DDD</code> | |||
[[Category:TachoSync]] | [[Category:TachoSync]] | ||