An 'Unexpected Error' occurs when approving C+ reports, but the reports are successfully approved.

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number:
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @garrettmknight
Slack conversation (hyperlinked to channel name): quality

Action Performed:

1. Approve a bunch of submitted C+ report

Expected Result:

All the reports got approved

Actual Result:

Unexpected Error’ message displayed for two reports
“Error processing command ‘Get’ (407 Missing authToken), ignoring.”

Workaround:

Unknown

Platforms:

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

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Logs

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @techievivek

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[melvin-bot]

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @techievivek (AutoAssignerNewDotQuality)

[melvin-bot]

@stephanieelliott, @techievivek Whoops! This issue is 2 days overdue. Let's get this updated quick!

[stephanieelliott]

Hey @techievivek can you take a look at this?

[techievivek]

Sorry, I forgot to post the updates here. I posted a comment in the linked slack thread, this seems to be an issue with authToken expiring when we are fetching the onyx updates for the user. I will bring a discussion in the #eng-chat channel to discuss this further.

[melvin-bot]

@stephanieelliott, @techievivek Eep! 4 days overdue now. Issues have feelings too...

[techievivek]

Not overdue, will investigate this again today.

[melvin-bot]

@stephanieelliott @techievivek this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot]

@stephanieelliott, @techievivek Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

@stephanieelliott, @techievivek 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[techievivek]

Looking into it now.

[techievivek]

Updates here https://expensify.slack.com/archives/C05LX9D6E07/p1735742835938139?thread_ts=1734003477.036259&cid=C05LX9D6E07, brought an internal discussion here https://expensify.slack.com/archives/C03TQ48KC/p1735746048891849

[techievivek]

Pushed a PR for adding some logs here https://github.com/Expensify/Web-Expensify/pull/44945, it is a widespread issue when we try to send push notification for IOU action.

[techievivek]

Discussions here https://expensify.slack.com/archives/C03TQ48KC/p1735746048891849

[techievivek]

We have a clear understanding of the issue now, I am discussing the solution with the team here https://expensify.slack.com/archives/C03TQ48KC/p1736145923335859?thread_ts=1735746048.891849&cid=C03TQ48KC

[melvin-bot]

@stephanieelliott, @techievivek Whoops! This issue is 2 days overdue. Let's get this updated quick!

[stephanieelliott]

Hey @techievivek have we come up with a solution for this one?

[techievivek]

Will provide an update today.

[melvin-bot]

@stephanieelliott, @techievivek Still overdue 6 days?! Let's take care of this!

[techievivek]

Pushed a PR for this.

[stephanieelliott]

PR is being actively reviewed

[melvin-bot]

@stephanieelliott, @techievivek Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@stephanieelliott, @techievivek Huh... This is 4 days overdue. Who can take care of this?

[stephanieelliott]

PR is on staging

[techievivek]

The PR is now live on PROD, and I have confirmed that the Error processing command 'Get' (407 Missing authToken) error log no longer appears in the push notification flow for IOUs or any other actions requiring an authToken. I will go ahead and close this.