You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Travel - No trip expenses created in workspace chat #82593
Version Number: v9.3.20-2 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/test-cases/41237918 Email or phone of affected tester (no customers): new expensifail account Issue reported by: Applause Internal Team Bug source: Regression TC Execution Device used: MacOS Monterey 12.7.4 / Chrome App Component: Other
Action Performed:
Precondition2:
Sign up new account in OldDot. Return to OldDot again after navigating to NewDot.
Create Worksapce, open DevTools console and run:
var settings = NVP.get('travelSettings') || {};
settings.testAccount = true;
NVP.set('travelSettings', settings);
Enable Travel feature in worksapce > More features
There're 2 expenses:
one of the expenses is for the price of the flight
one of the expenses is for 15$
Both expenses have receipts and the details match to what was booked
Please re-state the problem that we are trying to solve in this issue.
After booking a one-way flight through Expensify Travel (staging.travel.expensify.com), no expenses appear in the workspace chat. Expected behavior is two expenses (flight price + $15 booking fee), both with receipts matching the booking details.
What is the root cause of that problem?
After thorough investigation of the App codebase, trip expense creation is entirely server-side — the App frontend has zero logic for creating trip expenses and is purely a display layer. Here is how the flow works:
No client-side filtering would hide trip expenses once they exist in Onyx:
shouldReportActionBeVisible() explicitly returns true for TRIPPREVIEW and TRAVEL_UPDATE actions, bypassing all other visibility checks (src/libs/ReportActionsUtils.ts:1142-1144)
New expenses cannot be manually added to trip rooms — they only arrive from the backend (src/libs/ReportUtils.ts:9823)
The root cause is almost certainly server-side (Auth/Web-Expensify backend): the Spotnana booking webhook is either not being received, not being processed correctly, or the backend is failing to create the trip room / expense reports / transactions / TRIPPREVIEW action after the booking completes. This could be specific to one-way flights (missing return leg data causing a validation failure) or to the staging environment's Spotnana integration.
What changes do you think we should make in order to solve the problem?
Since the issue is server-side, the investigation needs to move to the backend repos (Auth/Web-Expensify). Specific steps:
Check backend logs for the Spotnana webhook receipt/processing after the test booking — verify whether the booking completion notification was received at all
Check if a trip room was created for the booking — if no trip room exists, the webhook handler failed
Check if the TRIPPREVIEW action was created in the workspace policy expense chat — if the trip room exists but no TRIPPREVIEW, the action creation logic has a bug
Check if expense reports and transactions were created with proper linkage (chatReportID → trip room, receipt.reservationList populated)
Investigate one-way flight edge case — the backend may have validation that expects return leg data and fails silently for one-way bookings
If the issue is confirmed as a backend-only problem (no Onyx data created), no App changes are needed — the fix would be in Auth/Web-Expensify webhook processing.
What alternative solutions did you explore? (Optional)
Checked for frontend regression: Examined all PRs merged between 9.3.18 and 9.3.20-2 that touched travel/trip code, report rendering, or report action visibility. No App-side changes could cause trip expenses to stop appearing — the TRIPPREVIEW visibility logic has not changed.
Checked for FlashList migration impact: PR Migrate MoneyRequestReportPreviewContent component to FlashList #81566 migrated MoneyRequestReportPreviewContent to FlashList in 9.3.20, but this affects REPORTPREVIEW actions (regular expenses), not TRIPPREVIEW actions which use a separate TripRoomPreview component.
What does the backend webhook handler do when processing a one-way flight booking from Spotnana? Is there missing error handling for flights without a return leg?
Is the $15 booking fee handled as a separate transaction or part of the flight transaction? If separate, there may be a different creation path for fee transactions.
Is this reproducible only on staging or also on production? The staging Spotnana integration may have a configuration issue.
Has this ever worked on staging, or is this the first time it was tested with the current Spotnana/backend setup?
Next Steps for Contributor+ team: This issue appears to be a server-side (backend) bug, not an App frontend issue. The App code correctly renders trip data when it exists in Onyx — the data is simply not being created. Investigation should continue in Auth/Web-Expensify repos to trace the Spotnana webhook processing. Reply with @MelvinBot <your feedback> to refine this analysis.
@CortneyOfstad@Ollyws 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!
FYI this was the cause of #fireroom-2026-02-27-travel-payloads, and was the only indicator that we had that Expensify Travel was completely broken for all customers. Since it wasn't escalated, 100% of our travel customers had a broken travel integration for 9 full days.
In the future we need to make sure that we consider the implications of the bug and try to prioritize accordingly
Activity
melvin-bot commentedon Feb 16, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws (
External)melvin-bot commentedon Feb 16, 2026
Triggered auto assignment to @CortneyOfstad (
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 commentedon Feb 16, 2026
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.
MelvinBot commentedon Feb 18, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
After booking a one-way flight through Expensify Travel (staging.travel.expensify.com), no expenses appear in the workspace chat. Expected behavior is two expenses (flight price + $15 booking fee), both with receipts matching the booking details.
What is the root cause of that problem?
After thorough investigation of the App codebase, trip expense creation is entirely server-side — the App frontend has zero logic for creating trip expenses and is purely a display layer. Here is how the flow works:
GenerateSpotnanaTokenAPI → opens Spotnana portal (src/libs/actions/Link.ts:122-145)chatType='tripRoom') withtripDatacontaining Spotnana payload (src/types/onyx/Report.ts:260-273), (b) IOU/expense reports withchatReportID→ trip room, (c) transactions withreceipt.reservationList, (d)TRIPPREVIEWaction in workspace chat withlinkedReportID→ trip room (src/types/onyx/OriginalMessage.ts:1027-1036)src/libs/actions/User.ts:926-951)No client-side filtering would hide trip expenses once they exist in Onyx:
shouldReportActionBeVisible()explicitly returnstrueforTRIPPREVIEWandTRAVEL_UPDATEactions, bypassing all other visibility checks (src/libs/ReportActionsUtils.ts:1142-1144)src/libs/ReportUtils.ts:9487)src/libs/ReportUtils.ts:9823)The root cause is almost certainly server-side (Auth/Web-Expensify backend): the Spotnana booking webhook is either not being received, not being processed correctly, or the backend is failing to create the trip room / expense reports / transactions /
TRIPPREVIEWaction after the booking completes. This could be specific to one-way flights (missing return leg data causing a validation failure) or to the staging environment's Spotnana integration.What changes do you think we should make in order to solve the problem?
Since the issue is server-side, the investigation needs to move to the backend repos (Auth/Web-Expensify). Specific steps:
TRIPPREVIEWaction was created in the workspace policy expense chat — if the trip room exists but noTRIPPREVIEW, the action creation logic has a bugchatReportID→ trip room,receipt.reservationListpopulated)If the issue is confirmed as a backend-only problem (no Onyx data created), no App changes are needed — the fix would be in Auth/Web-Expensify webhook processing.
What alternative solutions did you explore? (Optional)
MoneyRequestReportPreviewContentcomponent toFlashList#81566 migratedMoneyRequestReportPreviewContentto FlashList in 9.3.20, but this affectsREPORTPREVIEWactions (regular expenses), notTRIPPREVIEWactions which use a separateTripRoomPreviewcomponent.useReportAttributesperformance changes (PR [No QA] perf: replace reportsSelector with useReportAttributes hook #82551) and OpenReport improvements (PR Remove unused reportActions prop from PureReportActionItem #82263) were examined but only affect prop cleanup and selectors, not data availability.Open Questions
Next Steps for Contributor+ team: This issue appears to be a server-side (backend) bug, not an App frontend issue. The App code correctly renders trip data when it exists in Onyx — the data is simply not being created. Investigation should continue in Auth/Web-Expensify repos to trace the Spotnana webhook processing. Reply with
@MelvinBot <your feedback>to refine this analysis.Ollyws commentedon Feb 19, 2026
I agree with Melvin, seems to be a backend issue @CortneyOfstad
12 remaining items
melvin-bot commentedon Mar 2, 2026
@CortneyOfstad @Ollyws 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 commentedon Mar 6, 2026
@Ollyws Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Mar 10, 2026
@Ollyws 10 days overdue. I'm getting more depressed than Marvin.
CortneyOfstad commentedon Mar 11, 2026
@Ollyws can you comment to clear the Overdue label?
Ollyws commentedon Mar 12, 2026
👍
mvtglobally commentedon Mar 15, 2026
Issue not reproducible during KI retests. (First week)
CortneyOfstad commentedon Mar 16, 2026
I am unable to recreate either, so going to close as this appears to have been a one-off issue. Thank you!
stitesExpensify commentedon Mar 18, 2026
FYI this was the cause of #fireroom-2026-02-27-travel-payloads, and was the only indicator that we had that Expensify Travel was completely broken for all customers. Since it wasn't escalated, 100% of our travel customers had a broken travel integration for 9 full days.
In the future we need to make sure that we consider the implications of the bug and try to prioritize accordingly