Skip to main content
Version: Current

Known issues

Problems we know about, how to recognise them and how to fix them. If your problem is not listed, check the FAQ.

Trip is not synced: "Another trip is already being recorded" (HTTP 409)​

Symptoms​

  • A trip recorded in the app is marked Sync failed (German: Sync fehlgeschlagen) in the trip list and never appears on the server.
  • In the web dashboard there is a trip without end time and with 0 km – a recording that was started but never finished.
  • In the app log (Logcat, tag FahrtenbuchSync) you see 409 … TRACKING_ALREADY_ACTIVE together with the ID of that trip ("details":{"tripId":"…"}). The server's message there is always German: Es wird bereits eine Fahrt aufgezeichnet ("a trip is already being recorded").

Cause​

The server allows only one running recording per account. When the app starts syncing a trip, it first creates it on the server (POST /tracking/start). If the sync was interrupted right after that – for example because a second sync was triggered and cancelled the first, or the connection dropped before the answer arrived – the server kept an empty, unfinished trip, but the app never learned its ID.

From then on, every sync tried to create the trip again and was rejected because the empty trip was still "recording". This blocks all further trips of the account, not only the affected one.

Solution​

Delete the empty trip on the server; the app then transfers the trip completely with the next sync.

  1. Open the web dashboard and find the trip without end time and with 0 km. If you have the ID from the log, you can open it directly via its trip details.
  2. Check that it really is empty (no route, 0 km). Then choose Delete trip in the trip details. The trip is moved to the archive and is kept there for 90 days, so nothing is lost by mistake.
  3. Wait for the next sync: the app retries in the background as soon as it has a network connection, at the latest after about 15 minutes. The trip is then created on the server with all GPS points, purpose and tags, and the Sync failed mark disappears.

If the unfinished trip is a real trip (it has a route and distance), do not delete it: edit it in the web dashboard and enter an end time instead. That also ends the recording.

Automatic recovery​

The app and the server try to resolve this on their own:

  • Server: the app sends an ID generated on the device when the trip starts (clientTripId). A repeated start of the same trip returns the existing server trip instead of an error.
  • Android app: if the running server trip belongs to the same trip, the app takes it over. If it belongs to another trip of this device that was already ended there, the app finishes it first; if the device no longer has that trip, the app deletes the server copy (archive). Recordings from the web dashboard or other devices are never changed automatically – for those the app shows a hint.

This only works for trips that carry such a device ID and requires app and server to be up to date. If a trip still gets stuck – for example an older recording without device ID or one started in the web dashboard – remove or end it as described above.