Skip to content

[Payment due @brunovjk] Show Explain button on receipt scan failed system messages - #93532

Merged
mollfpr merged 5 commits into
mainfrom
beaman/612790-app-smartscan-explain
Jun 23, 2026
Merged

mollfpr merged 5 commits into
mainfrom
beaman/612790-app-smartscan-explain

Conversation

@Beamanator

@Beamanator Beamanator commented Jun 13, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

When SmartScan fails to parse a receipt, Auth posts a RECEIPTSCANFAILED report action in the transaction thread. As of Auth PR 21123 (merged 2026-06-13), that action now carries a reasoning field on originalMessage — an LLM-friendly description of what was/wasn't extracted — and hasReasoning(action) is what activates the inline Explain affordance everywhere else in the App.

The gap before this PR: ReceiptScanFailedContent rendered the action with a plain ReportActionItemBasicMessage, which has no hasReasoning() awareness. So reasoning was being delivered but the inline Explain link never appeared. (The right-click / long-press context menu's Explain entry — which gates on hasReasoning(reportAction) directly in ContextMenuActions.tsx — was already working, but the much more discoverable inline affordance was not.)

This PR:

  1. In ReceiptScanFailedContent.tsx — when hasReasoning(action) is true, renders through ReportActionItemMessageWithExplain (passing action, childReport, and originalReport), matching the pattern used by MovedTransactionAction, ExportIntegration, ModifiedExpenseContent, UnreportedTransactionAction, and ApprovalFlowContent. Otherwise falls back to the existing ReportActionItemBasicMessage rendering.
  2. In ActionContentRouter.tsx — threads originalReport down to ReceiptScanFailedContent (required by the WithExplain wrapper's explain() call).
  3. In src/types/onyx/OriginalMessage.ts — adds reasoning?: string to OriginalMessageSmartScanFailed for type accuracy. (Behaviour unchanged: the runtime hasReasoning() check is 'reasoning' in originalMessage, so this is type hygiene, not a behavioral fix.)

The user-visible message string is unchanged — translate('violations.smartscanFailed', {canEdit, missingFields}) still drives the human-readable copy (Receipt scanning failed — missing <fields>. Enter details manually.) for both branches.

Parent feature: the Explain feature rollout.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/612790
PROPOSAL:

Tests

These are reproducible against a local dev build where the merged Auth PR is deployed (i.e. the Auth service on staging/prod, or the local Auth checkout past commit d67a2a0b).

  1. Sign in as a user able to submit receipts (no scan-limit gate, validated email).
  2. From a 1:1 DM or workspace chat, start a new submit-expense flow and upload a receipt that SmartScan cannot parse. Reliable options:
    • Upload a screenshot of a non-receipt image (e.g. a chat screenshot).
    • Upload a blank or solid-colour image.
    • Upload a heavily blurred or partially cropped real receipt.
  3. Wait for SmartScan to finish (typically 30s–2 minutes). The transaction thread will receive a system message from Concierge.
  4. Open the transaction thread (tap the expense preview to drill in).
  5. Confirm the system message reads: Receipt scanning failed — missing <field(s)>. Enter details manually. — the exact field list reflects what couldn't be extracted (one of merchant, date, amount, or multiple).
  6. Core verification: confirm an inline Explain link is appended after that message (rendered as a muted, clickable link).
  7. Tap the Explain link.
  8. Confirm a thread opens off the system message and Concierge replies with a field-aware explanation referencing the specific missing fields — e.g. "The date couldn't be read from this receipt..." rather than the generic "Receipt scanning failed". This is the reasoning field round-tripping through the Explain flow.
  9. Regression check: long-press (mobile) or right-click (web) the system message and confirm the context menu still shows the Explain option (this path was already working pre-PR via ContextMenuActions.tsx and must not break).
  10. Backward-compat check: if your account has any historical RECEIPTSCANFAILED action from before the merged Auth PR (i.e. no reasoning field on originalMessage), confirm it renders the same as before — message text only, no inline Explain link.
  • Verify the inline Explain link is present on a freshly-failed scan.
  • Verify tapping Explain opens a Concierge thread with a field-aware reply.
  • Verify the context-menu Explain entry still works (regression).
  • Verify legacy scan-failed actions without reasoning render without the inline link (backward compat).
  • Verify no errors appear in the JS console.

Offline tests

Tapping Explain is a normal Concierge round-trip; offline behaviour mirrors any other Explain action (e.g. Moved transaction, Exported to integration):

  1. With network on, trigger a SmartScan failure and confirm the system message + inline Explain link render in the transaction thread.
  2. Disable network (airplane mode / browser devtools "Offline").
  3. Re-open the same transaction thread — confirm the system message and the inline Explain link still render from cached Onyx data.
  4. Tap Explain while offline — the action should be queued (no immediate Concierge response).
  5. Re-enable network — confirm Concierge's reply appears in the newly opened thread once requests flush.

QA Steps

QA can run against staging once the merged Auth PR has deployed.

  1. Sign in to staging on a test account that can submit receipts.
  2. From a chat, upload a non-receipt image (a screenshot, blank image, or low-quality receipt photo) via the receipt-attach flow.
  3. Wait for SmartScan to finish — the failure system message will appear in the transaction thread.
  4. Open the transaction thread.
  5. Verify the message reads Receipt scanning failed — missing <field(s)>. Enter details manually. and the exact missing-field list matches what was undetectable.
  6. Verify an inline Explain link is present immediately after the message text.
  7. Tap Explain.
  8. Verify a thread opens off the system message and Concierge responds with a field-aware explanation (the reply must reference the specific missing fields, not the generic copy).
  9. Long-press (mobile) or right-click (web) the system message — verify the context-menu Explain entry is also still present (regression check).
  10. Verify no errors appear in the JS console.
  • All steps above succeed on staging.
  • No console errors during the flow.

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline tests section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (backward-compat check for legacy actions without reasoning; offline tap-Explain behavior)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick) — N/A, no new callbacks
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method — no new copy added; existing violations.smartscanFailed translation reused
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message: — N/A, no new text added
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods — N/A
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue) — N/A, no new copy
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README. — N/A, no new files
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers — N/A, reused the existing hasReasoning + ReportActionItemMessageWithExplain pattern
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected) — the new originalReport prop on ReceiptScanFailedContent is required and supplied at the only call site in ActionContentRouter.tsx; no other consumers exist
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly — ReceiptScanFailedContent's prop type gained the required originalReport field; updated at its single call site
  • If any new file was added I verified that: — N/A, no new files
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that: — N/A, no new styles
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that: — N/A, no asset changes
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic. — N/A, system-message rendering only, no markdown-input path touched
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases) — N/A, modifies an action-specific renderer, not a generic component
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected. — N/A, no Storybook stories for this component
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account. — N/A, system message rendering only
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles: — adds an inline link via the existing ReportActionItemMessageWithExplain wrapper; no new buttons, no padding/spacing changes, no new form input styles
    • I verified that all the inputs inside a form are aligned with each other. — N/A
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes. — N/A, reuses an existing affordance unchanged
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page. — N/A, no new page
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

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

The .reasoning field is now populated on RECEIPTSCANFAILED actions by
Auth #21123, but ReceiptScanFailedContent renders via the bare
ReportActionItemBasicMessage which does not check hasReasoning().
Switch to ReportActionItemMessageWithExplain when reasoning is present
so users see the inline Explain link and can thread on the message.
@codecov

codecov Bot commented Jun 13, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
...nbox/report/actionContents/ActionContentRouter.tsx 94.11% <ø> (+3.09%) ⬆️
...report/actionContents/ReceiptScanFailedContent.tsx 100.00% <100.00%> (ø)
... and 348 files with indirect coverage changes

@Beamanator

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 2601cc786e

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@Beamanator
Beamanator marked this pull request as ready for review June 13, 2026 18:27
@Beamanator
Beamanator requested review from a team as code owners June 13, 2026 18:27
@melvin-bot
melvin-bot Bot requested review from brunovjk and heyjennahay and removed request for a team June 13, 2026 18:27
@melvin-bot

melvin-bot Bot commented Jun 13, 2026

Copy link
Copy Markdown

@brunovjk Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team June 13, 2026 18:27
@brunovjk

Copy link
Copy Markdown
Contributor

Reviewing ASAP. Thanks

@Beamanator

Copy link
Copy Markdown
Contributor Author

quick bump @brunovjk 🙏

@brunovjk

brunovjk commented Jun 17, 2026 •

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
93532_android_native.mov
Android: mWeb Chrome
93532_android_web.mov
iOS: HybridApp
iOS: mWeb Safari
93532_ios_web.mov
MacOS: Chrome / Safari
93532_web_chrome.mov

@brunovjk

Copy link
Copy Markdown
Contributor

@Beamanator do you think we can increase test coverage here? Thanks.

@Beamanator

Copy link
Copy Markdown
Contributor Author

ooooh ya good plan :D

@brunovjk

brunovjk commented Jun 17, 2026 •

Copy link
Copy Markdown
Contributor

We are adding an extra period (.) to the end of the sentence:
Screenshot 2026-06-17 at 13 27 51

Just to confirm, should the button be available inside the thread?

Screen.Recording.2026-06-17.at.13.28.02.mov

Thank you.

@brunovjk

Copy link
Copy Markdown
Contributor

One more thing, every time we press the "Explain" button, we send the same message over again. Is this intentional? Thank you.

Screen.Recording.2026-06-17.at.13.33.56.mov

Adds four UI tests for RECEIPT_SCAN_FAILED in ReportActionItemTest.tsx:
submitter + reasoning shows Explain, non-submitter + reasoning shows
Explain (guards both canEdit branches), no reasoning hides Explain
(backward compat for pre-Auth-21123 actions), and missingFields +
reasoning shows the field-specific message alongside Explain.

Matches the existing MOVED_TRANSACTION / APPROVED / EXPORTED_TO_INTEGRATION
Explain test patterns in the same file.
@Beamanator

Copy link
Copy Markdown
Contributor Author

Ok so i def need to remove the dupe period, will work on that 👍

As for the Should Explain also appear inside the thread? - yes, it should since it should be the same exact text as the parent report comment - are you thinking we follow a different convention elsewhere?

And as for Pressing Explain re-sends the same message every time - same, yes for now it resends the same comment every time i believe in ALL uses of the Explain button. Maybe we'll have to improve this eventually - but for now yes it's expected

The `smartscanFailed` translation always ends with a period (e.g.
"…Enter details manually."), and `AskToExplain` prepends its own
leading ". Explain", so the rendered string came out as
"…manually.. Explain" — two periods.

Other Explain-using flows (MovedTransaction, ExportIntegration, etc.)
don't hit this because their underlying message strings don't end
in a period. Stripping the trailing period in the WithExplain branch
of ReceiptScanFailedContent keeps the fix narrow to this caller.

Adds a regression test that asserts the rendered DOM does not contain
".. Explain", mirroring the existing EXPORTED_TO_INTEGRATION guard.
main now requires chatReport as a prop on ReportActionItem (commit
8aad255, lift up chatReport), and main's version of this test
file already passes chatReport={undefined} to every existing usage.
The five new RECEIPT_SCAN_FAILED tests I added were missing the prop,
so the PR-merged-with-main typecheck failed on each of them.
@Beamanator

Copy link
Copy Markdown
Contributor Author

ok i think this is ready for you again @brunovjk !

@brunovjk brunovjk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I do wonder whether removing the leading period from AskToExplain would be a cleaner solution than trimming the message here. That said, it may have a wider impact on other usages and would probably be out of scope for this PR. What do you think, @Beamanator?

@melvin-bot
melvin-bot Bot requested a review from neil-marcellini June 18, 2026 14:08
@melvin-bot

melvin-bot Bot commented Jun 18, 2026

Copy link
Copy Markdown

@neil-marcellini Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot changed the title Show Explain button on receipt scan failed system messages [Payment due @brunovjk] Show Explain button on receipt scan failed system messages Jun 18, 2026
@melvin-bot

melvin-bot Bot commented Jun 18, 2026

Copy link
Copy Markdown

🎯 @brunovjk, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/612790.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

@Beamanator

Copy link
Copy Markdown
Contributor Author

LGTM. I do wonder whether removing the leading period from AskToExplain would be a cleaner solution than trimming the message here. That said, it may have a wider impact on other usages and would probably be out of scope for this PR. What do you think, @Beamanator?

Yeah def an interesting thought and could be nice to update at some point, but as you said - probably not in this PR since it would require updating other usages of the Explain feature and we don't wanna add that to this PR specifically 👍

All you @neil-marcellini !

@Beamanator

Copy link
Copy Markdown
Contributor Author

Actually @brunovjk i'm seeing this in the failing check - can you take a look?:

You completed 57 out of 50 checklist items with 0 unfinished items
Make sure you are using the most up to date checklist found here: https://raw.githubusercontent.com/Expensify/App/main/contributingGuides/REVIEWER_CHECKLIST.md

@brunovjk brunovjk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I redid the checklist now. I approved it again to trigger another run.

@neil-marcellini
neil-marcellini requested review from a team and removed request for neil-marcellini June 22, 2026 21:25
@melvin-bot
melvin-bot Bot requested review from jayeshmangwani and removed request for a team June 22, 2026 21:25
@melvin-bot

melvin-bot Bot commented Jun 22, 2026

Copy link
Copy Markdown

@jayeshmangwani Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@neil-marcellini

Copy link
Copy Markdown
Contributor

I re-assigned this because I currently have 14+ PRs to review and I do not want to slow things down while I catch up on reviews. Pullerbear didn't work to get a new internal engineer, so if you really need someone I can review tomorrow.

@neil-marcellini
neil-marcellini removed the request for review from jayeshmangwani June 22, 2026 21:27
@Beamanator

Copy link
Copy Markdown
Contributor Author

no worries! i'll find a new reviewer!

@mollfpr
mollfpr merged commit 5351d7b into main Jun 23, 2026
47 of 49 checks passed
@mollfpr
mollfpr deleted the beaman/612790-app-smartscan-explain branch June 23, 2026 15:13
@github-actions

Copy link
Copy Markdown
Contributor

🚧 @mollfpr has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify OSBotify mentioned this pull request Jun 23, 2026
48 tasks done
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mollfpr in version: 9.4.18-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 I reviewed this PR against the help site articles under docs/articles.

Docs update required: Yes. This PR surfaces a discoverable inline Explain link on RECEIPTSCANFAILED system messages, but the relevant help article — Troubleshoot SmartScan Issues — only documented the failure message and the retry flow, not the new Explain affordance.

Draft PR: #94377

It adds a task-based ## How to understand why a SmartScan failed section to Troubleshoot-SmartScan-Issues.md, documenting the inline Explain link and the field-aware Concierge reply it opens. I verified the label is exactly Explain against common.explain in src/languages/en.ts, reused the existing failure-message copy verbatim, and followed HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md (single # title, task-based ## heading, screenshot placeholder as a non-rendered comment).

@Beamanator, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review.

@jponikarchuk

Copy link
Copy Markdown

Deploy Blocker #94411 was identified to be related to this PR.

@brunovjk

Copy link
Copy Markdown
Contributor

Deploy Blocker #94411 was identified to be related to this PR.

I don’t think this is a regression from our PR. I commented on the issue, explaining a bit of what I think.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.4.18-2 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@melvin-bot

melvin-bot Bot commented Jun 24, 2026

Copy link
Copy Markdown

🤖 Payment issue created: #94492

@quinthar quinthar added the #ai label Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants