[Due for payment 2026-03-19] [Due for payment 2026-02-27] Sentry spans taking hours/days before they are closed or cancelled

[rlinoz]

We can see it here https://expensify.sentry.io/explore/traces/?environment=staging&environment=production&project=4510228107427840&query=span.duration%3A%3E10h&statsPeriod=24h that we have a ton of spans that takes more than 10 hours to get resolved.

This points to a problem in our implementation, but more than that it makes our metrics innacurate. Let's find out what is happening and get it fixed.

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

@sosek108 Eep! 4 days overdue now. Issues have feelings too...

[rlinoz]

This is still true, we are trying to add logs to check what is happening, rigth @sosek108 ?

[melvin-bot]

This issue has not been updated in over 14 days. @sosek108 eroding to Weekly issue.

[rlinoz]

This is still daily, we just added a way to cancel all spans when moving to backgroundc though, so this might be solved.

[rlinoz]

Hey @sosek108 as we discussed things are much better after the last PR https://expensify.sentry.io/explore/traces/?cursor=0%3A0%3A1&environment=staging&field=id&field=span.name&field=span.description&field=span.duration&field=transaction&field=timestamp&field=tags%5Bcanceled%2Cnumber%5D&project=4510228107427840&query=release%3Anew.expensify%409.3.16-0%20span.duration%3A%3E10min%20%21has%3Atags%5Bcanceled%2Cnumber%5D%20span.status%3Aok&statsPeriod=24h

But apparently we don't cancel a lot of the loading spans, are you able to look into it?

[sosek108]

Yes, I have this on my backlog