Taxes - Tax rate and tax amount take some time to show up in transaction thread

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 1.4.60-1
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• User is an employee of Collect workspace that has taxes.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a manual request with tax.
4. Go to transaction thread immediately after the request is created.

Expected Result:

Tax rate and tax amount will instantly show up in transaction thread.

Actual Result:

Tax rate and tax amount take some time to show up in transaction thread.

Workaround:

n/a

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6437960_1712235526985.bandicam_2024-04-04_20-55-53-264.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~013d484f5c32510e05
• Upwork Job ID: 1775993187810840576
• Last Price Increase: 2024-04-04

[melvin-bot]

Triggered auto assignment to @flodnv (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[kbecciv]

We think that this bug might be related to #wave-collect - Release 1

[MonilBhavsar]

Not a blocker, i think
We'll be fixing as a regression from #33927

[alitoshmatov]

This is related to offline updates which was not on scope of mentioned PR, and is going to be handled separately, ref: #33927 (comment)