Skip to content

Travel - Book Flight is stuck on waiting for a confirmation from the airline #101844

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: v9.4.91-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod - Provide reasoning.
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13177079/detail-test-case/41237918
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 11 / Chrome, Android 13 / Xiaomi Poco F5, iOS 18.4.1 / iPhone 11 Pro
App Component: Other

Action Performed:

Precondition:

  • Already create account and add necessary details required for Travel

Steps

  1. Click FAB > Book Travel to open the Travel home page
  2. Search for a flight from SEA to SFO for a date one month in the future
  3. Select an Alaska Airlines flight
  4. Complete all required information to complete the booking
  5. Book the flight
  6. Wait for a few minutes

Expected Result:

Book Flight can be completed after waiting a few minutes

Actual Result:

Book Flight is stuck on waiting for a confirmation from the airline.
Note:

  • In ND, only the trip summary preview appears in the workspace chat, and no information is shown when it is opened
  • No trip expenses are created in the workspace chat

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7265789_1790027419001.101773_-_Travel_-_Book_Flight_is_stuck_on_waiting_for_a_confirmation_from_the_airline.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7265789

Issue OwnerCurrent Issue Owner: @NicolasBonet

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 22, 2026
  2. applause-bot commented on Sep 22, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/ed74b379fdcf23c6587a22cf4e4ee99e8cd1b1b02dc66e248a865dacdf27942e

  3. MelvinBot commented on Sep 22, 2026

    @MelvinBot
    Contributor

    Issue Analysis

    This is not an App bug, and it can't be fixed in this repo. The "waiting for a confirmation from the airline" screen is rendered by TravelDot/Spotnana at travel.expensify.com, not by NewDot. App's entire role is to mint a token and hand off — src/components/BookTravelButton.tsx:171 → src/libs/actions/Link.ts:73-121 (new tab on web, WebView on native). App has no booking-status polling, no pending-confirmation state, and no copy matching that string.

    The two NewDot symptoms are downstream effects of the booking never ticketing, not separate bugs. Reservations come only from backend-pushed data at src/libs/TripReservationUtils.ts:506-514 — reportNameValuePairs.tripData.payload.pnrs or transaction.receipt.reservationList. With no confirmed PNR, both are empty, so the preview shows "0 trips" / $0 and the trip room renders a bare "Trip summary" heading.

    Next step: escalate to an internal engineer. Someone with backend access needs to check, for this tester's tripID, whether Spotnana ever sent a ticketing/BOOKING_TICKETED webhook. Worth ruling out first: test accounts are routed to staging.travel.expensify.com with the staging TMC ID (src/CONST/index.ts:6438-6443), and sandbox bookings routinely hang in a pending state and never ticket.

    Investigation details

    Why the fix isn't in App

    The only App files in the travel path are BookTravelButton.tsx, openTravelDotLink/index.ts + index.native.ts, libs/actions/Link.ts, and pages/Travel/TravelDotLinkWebview.tsx. None render booking status. App's only travel API commands are GenerateSpotnanaToken, AcceptSpotnanaTerms, RequestTravelAccess, and UpdateTripRoomName — there is no trip-fetch or booking-status command, and no setInterval/polling anywhere in the travel code. App's travel constants have no pending/awaiting-confirmation concept at all (PNR_STATUS only has CANCELLED/VOIDED). A repo-wide grep for "confirmation from the airline" returns zero hits in src/.

    Trip data reaches App only as reportNameValuePairs.tripData written by the backend from the Spotnana payload. The TRIPPREVIEW report action itself carries only a linkedReportID — no trip data — so a preview created before ticketing necessarily points at an empty room.

    Rendering chain when the payload is missing

    • Workspace chat: TripRoomPreview.tsx:193-196 → "· 0 trips", reservation list hidden by the length > 0 guard, total falls back to $0.00.
    • Opening it: TripDetailsView.tsx:271-272 maps over an empty array — heading only, no crash, no empty state. That is exactly "no information is shown when it is opened."

    Alternative explanations considered

    Could this be an App rendering bug rather than a missing PNR? No — the same getReservationsFromTripReport chokepoint feeds the preview, the trip room, and the Upcoming Travel widget, and App cannot fetch the data it would need. Could App be dropping an Onyx update? Possible in principle, but it would still require backend logs to distinguish "payload never sent" from "payload sent and not persisted" — that check is the recommended next step above.

    Not reproduced: verifying this end to end requires completing a real airline booking, so no test run was attempted.

    Secondary App-side gaps (not the fix, worth separate issues)

    1. No empty/pending state in TripDetailsView — a stalled booking looks like a blank screen instead of saying the booking isn't confirmed yet. This is the only part of the reported symptom App could improve.
    2. DynamicTripSummaryPage.tsx:47 uses shouldShow={reservationsData.length === 0 || !CONFIG.IS_HYBRID_APP}, while every comparable site pairs the hybrid check with the beta check (see DynamicTripDetailsPage.tsx:102). As written, the Trip summary page shows "not found" unconditionally on standalone/web builds. Pre-existing.

    Related issues: a scan of open and recently closed App issues for this symptom found no duplicates.


    Next Steps: Reply with @MelvinBot <your feedback> to refine this analysis.


    view run

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Sep 22, 2026
  5. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)

  6. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

  7. melvin-bot commented on Sep 25, 2026

    @melvin-bot

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

  8. melvin-bot commented on Sep 29, 2026

    @melvin-bot

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

  9. melvin-bot commented on Oct 1, 2026

    @melvin-bot

    @eVoloshchak 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  10. eVoloshchak commented on Oct 2, 2026

    @eVoloshchak
    Contributor

    This is not an App bug, and it can't be fixed in this repo. The "waiting for a confirmation from the airline" screen is rendered by TravelDot/Spotnana at travel.expensify.com, not by NewDot.
    Next step: escalate to an internal engineer. Someone with backend access needs to check, for this tester's tripID, whether Spotnana ever sent a ticketing/BOOKING_TICKETED webhook.

    Agree with Melvin's assessment; this needs to be internal

    🎀 👀 🎀 C+ reviewed"

  11. melvin-bot commented on Oct 2, 2026

    @melvin-bot

    Triggered auto assignment to @NicolasBonet, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  12. NicolasBonet commented on Oct 2, 2026

    @NicolasBonet
    Contributor

    I checked the backend logs for the booking in this report (trip 6739129112, booked on 2026-09-22 around 02:45 UTC).

    Spotnana never sent the ticket-issued webhook (BOOKING_TICKETED) for this trip, so this isn't an App or backend bug.

    • We received only BOOKING_CREATED and BOOKING_OTHER_UPDATE.
    • In the last update Spotnana sent, the booking and flight were both still PROCESSING_STATUS. The airline status on the segment was UC (unable to confirm), and the ticket list was empty.
    • The airline never confirmed the seat, which is why TravelDot showed "waiting for a confirmation from the airline".

    The NewDot symptoms follow from that, and they're the intended behaviour:

    • We create a flight expense only when the ticket is issued, so no expense was created.
    • The trip room is created when Spotnana reports the booking, but its details are only filled in once the booking has confirmed reservations. That's why the preview showed "0 trips" and the room was empty.

    Ticketing in Spotnana's test environment dropped almost to zero around Sept 19–22. It's been working again since, with test bookings ticketing and creating expenses normally.

    @Expensify/applauseleads could you please retest this? If a booking gets stuck in "waiting for a confirmation from the airline" again, please include the trip ID so we can trace it.

  13. NicolasBonet commented on Oct 5, 2026

    @NicolasBonet
    Contributor

    Not overdue, waiting for a re-test/

  14. m-natarajan commented on Oct 5, 2026

    @m-natarajan

    Chrome / v9.5.2-2, Passed

    bandicam.2026-10-05.20-32-05-196.mp4
  15. NicolasBonet commented on Oct 5, 2026

    @NicolasBonet
    Contributor

    Closing then, thank you @m-natarajan!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions