[Due for payment 2026-03-30] ManualCreateExpenseSubmit telemetry span includes GPS wait time, making the metric unreliable

[marcaaron]

Problem

When a user submits an expense that requires geolocation, the ManualCreateExpenseSubmit telemetry span includes the full GPS wait time (typically 5-30 seconds). This makes the metric useless for measuring actual submit performance, since the real submit logic only takes a couple milliseconds.

Solution

End the ManualCreateExpenseSubmit span right after the submit is dispatched, before the GPS lookup begins. Track GPS latency separately under a new ManualGeolocationWait child span so it can be measured independently. This applies to both the track expense and request money code paths.

Issue Owner

Current Issue Owner: @BartekObudzinski

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.41-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [No QA] perf: Isolate GPS wait from ManualCreateExpenseSubmit telemetry span #84415

If no regressions arise, payment will be issued on 2026-03-30. 🎊

For reference, here are some details about the assignees on this issue:

• @BartekObudzinski does not require payment (Contractor)

[melvin-bot]

Triggered auto assignment to @mallenexpensify (Awaiting Payment)