Retroactive Cost Update for Geofence kWh Cost Fails Silently

[CAEck]

Is there an existing issue for this?

• I have checked the existing issues and discussions, and I can confirm that there are no duplicates.

What happened?

When editing the kWh cost for a geofence in TeslaMate, a popup appears asking if the new cost should be applied retroactively to all existing charge sessions at that location. If the user clicks "Continuer" to not apply the new cost retroactively (i.e., only to future charges), the system does not provide a clear way to confirm this choice. The UI seems to process something in the background, but the new cost is not applied to future sessions as expected.

Expected Behavior

No response

Can the issue reliably be reproduced?

Yes

Steps To Reproduce the issue

Go to the geofence edit page in TeslaMate.
Change the kWh cost for a location.
A popup appears: "Il existe 26 sessions de charge à cet endroit pour lesquelles aucun coût n’a encore été ajouté. Ajouter les coûts rétroactivement ?"
Click "Continuer" (Continue) to not apply the retroactive update.
TeslaMate works in the background and returns control to the UI after some time.
Check the charge sessions: the cost for past sessions remains unchanged.

Relevant log output

teslamate-1  | 2026-04-09 05:00:17.458 [error] GenServer #PID<0.1109865.0> terminating
teslamate-1  | ** (Postgrex.Error) ERROR 57014 (query_canceled) canceling statement due to user request
teslamate-1  |     (ecto_sql 3.13.4) lib/ecto/adapters/sql.ex:1113: Ecto.Adapters.SQL.raise_sql_call_error/1
teslamate-1  |     (teslamate 3.0.0) lib/teslamate/locations.ex:155: TeslaMate.Locations.apply_geofence/2
teslamate-1  |     (teslamate 3.0.0) lib/teslamate/locations.ex:197: anonymous fn/3 in TeslaMate.Locations.update_geofence/2
teslamate-1  |     (teslamate 3.0.0) lib/teslamate/repo.ex:2: anonymous fn/1 in TeslaMate.Repo.transaction/2
teslamate-1  |     (ecto 3.13.5) lib/ecto/repo/transaction.ex:11: anonymous fn/3 in Ecto.Repo.Transaction.transact/4
teslamate-1  |     (ecto_sql 3.13.4) lib/ecto/adapters/sql.ex:1473: anonymous fn/3 in Ecto.Adapters.SQL.checkout_or_transaction/4
teslamate-1  |     (db_connection 2.9.0) lib/db_connection.ex:1747: DBConnection.run_transaction/4
teslamate-1  |     (teslamate 3.0.0) lib/teslamate_web/live/geofence_live/form.ex:158: TeslaMateWeb.GeoFenceLive.Form.save/1
teslamate-1  | Last message: %Phoenix.Socket.Message{topic: "lv:phx-GKSXguSMTxcY1NqD", event: "event", payload: %{"event" => "calc-costs", "type" => "click", "value" => %{"result" => "no", "value" => ""}}, ref: "12", join_ref: "4"}

Screenshots

No response

Additional data

No response

Type of installation

Docker (https://docs.teslamate.org/docs/installation/docker/)

Version

3.0.0

PostgreSQL version

17

Are you running latest major supported PostgreSQL version?

• I run the latest major supported PostgreSQL version

Are you using a reverse Proxy for TeslaMate?

No

Details about your reverse Proxy if applicable

No response

[JakobLichterfeld]

Thanks for reporting.

The logs indicate exactly what you want, not updating the old entries:

** (Postgrex.Error) ERROR 57014 (query_canceled) canceling statement due to user request