Travel - Unable to book travel, an error occurred

[lanitochka17]

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: 9.0.90-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #55300
Email or phone of affected tester (no customers): new expensifail account
Issue reported by: Applause - Internal Team
Component: Other

Action Performed:

Precondition: use new accounts: owner of a workspace and 1 or more admins, with logins from the same private domains that never used Travel before.

1. ND: Sign in with one of the admins account
2. OD: Sign in with one of the admins account and run script on workspace tab:
   NVP.set('travelSettings', {'testAccount': true});
3. ND: Go to the Travel page and click the Book Travel button
4. ND: Enter address
5. ND: Accept the Terms and Conditions > click Continue

Expected Result:

Travel page is opened in a different tab

Actual Result:

An error 'Something went wrong'

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

Bug6726620_1738091465959.bandicam_2025-01-28_20-39-58-971.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @trjExpensify (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.

[stitesExpensify]

Hey @lanitochka17 can you please update any travel-related QA steps to use this script

var settings = NVP.get('travelSettings') || {};
settings.testAccount = true;
NVP.set('travelSettings', settings);

Instead of the current NVP.set('travelSettings', {'testAccount': true});?

[lanitochka17]

@stitesExpensify ok

[stitesExpensify]

Thank you! This should prevent accidental deletion of any existing travel data and prevent false-positives :)

[stitesExpensify]

Soon this won't be a problem because we will set the entirety of @applause.expensifail.com to be a test domain

[trjExpensify]

@stitesExpensify are you saying this bug is known, or asking for a retest from Applause after following those steps?

[stitesExpensify]

Yes, I don't think we need to keep this open. Travel is definitely still working on both prod and staging

[IuliiaHerets]

QA team can repro this issue in the latest build (v9.1.18-3), used account [email protected]

58899-Web.mp4

[trjExpensify]

Soon this won't be a problem because we will set the entirety of @applause.expensifail.com to be a test domain

@stitesExpensify did we do this then?

[stitesExpensify]

Yes, we did do that. I'll look into why this error happened

[stitesExpensify]

'412 Can't provision Travel for the default workspace'

It looks like we asked the user to upgrade, created a new policy, and then didn't set it to be their default.

[stitesExpensify]

cc @shubham1206agra since you worked on that feature

[melvin-bot]

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

[trjExpensify]

Okay cool, @shubham1206agra can you take care of this one?

[trjExpensify]

Looks legit. Logs.

Request:

Bedrock\Client - Starting a request ~~ command: 'AcceptSpotnanaTerms' clusterName: 'auth' headers: '[authToken: '<REDACTED>' policyID: '2DE18B331326C23A' domainName: '' isInNewProvisioningBeta: '' idempotent: '' logParam: '[email protected]' urlToNewDot: 'https://staging.new.expensify.com/' shouldReadUsingThreads: '' shouldHandleOnyxUpdates: '1' isNewDotRequest: '1' clientUpdateID: '4582077851' maxNumberOfUpdates: '500' requestID: '92606d7fcb61020f-LAX' lastIP: '31.128.188.165' writeConsistency: 'ASYNC' priority: '500' timeout: '110000']'

That policyID:

[shubham1206agra]

@stitesExpensify Let's hold this issue for #57537.

[trjExpensify]

Oh wow, that PR still isn't done? Commented.

[trjExpensify]

The PR we were held on was deployed last week. @shubham1206agra can you confirm that we can close this issue then?

[shubham1206agra]

@trjExpensify Yes

[trjExpensify]

Cool, closing.