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
[Due for payment 2026-07-29] [$250] Explain inline link missing on integration sync failure (INTEGRATION_SYNC_FAILED) messages #96422
Export/sync failure system messages (e.g. failed to export this report to NetSuite ("NS0196 Sync Error: …")) show the right-click "Explain" option but not the inline "Explain" link on hover. Since most users discover Explain via the inline link rather than the context menu, this affordance is effectively hidden for these messages even though the reasoning payload is present.
Root cause
The two affordances are gated differently:
Right-click "Explain" — ContextMenuActions.tsx gates the entry solely on hasReasoning(reportAction) with no per-type whitelist, so it fires for any action carrying a reasoning payload.
Inline "Explain" link — only renders when the action's render component explicitly wraps its message in <ReportActionItemMessageWithExplain> (e.g. ExportIntegration for the success path EXPORTED_TO_INTEGRATION).
The failure path routes to IntegrationSyncFailedMessage.tsx, which renders plain muted text via ReportActionItemBasicMessage + RenderHTML with noReportActionItemMessageWithExplain wrapper and no hasReasoning check:
This is not a regression — the failure/sync path was never whitelisted for the inline affordance. The 2026-04-29 auto-export commit (281da4f7) only wired the inline Explain into ExportIntegration (the success path).
Proposed fix
In IntegrationSyncFailedMessage.tsx, wrap the message in ReportActionItemMessageWithExplain when hasReasoning(action) is true (mirroring ExportIntegration.tsx), falling back to the current ReportActionItemBasicMessage / RenderHTML rendering when there's no reasoning. This turns on the inline Explain link for NetSuite/QBO sync-failure messages so users get it as a first-class hover action.
What it does: Makes IntegrationSyncFailedMessage.tsx mirror ExportIntegration.tsx — when hasReasoning(action) is true it wraps the message in ReportActionItemMessageWithExplain (which renders the inline "Explain" link and wires up the explain handler), and otherwise falls back to the existing muted-text rendering. ActionContentRouter.tsx now passes originalReport through so the handler has the report context it needs.
Validation
npm run lint-changed — passed
npm run typecheck-tsgo — passed
npm run react-compiler-compliance-check check <changed files> — passed
Jest could not be run in this environment. The existing INTEGRATION_SYNC_FAILED UI test in tests/ui/ReportActionItemTest.tsx exercises the no-reasoning path, which is unchanged (still renders via ReportActionItemBasicMessage), so it remains valid.
Please add manual Tests/QA steps and mark it Ready for review when it's ready — PullerBear will then assign the reviewer.
changed the title [-]Explain inline link missing on integration sync failure (`INTEGRATION_SYNC_FAILED`) messages[/-][+][$250] Explain inline link missing on integration sync failure (`INTEGRATION_SYNC_FAILED`) messages[/+]on Jul 19, 2026
Activity
marcaaron commentedon Jul 17, 2026
@MelvinBot please implement this.
MelvinBot commentedon Jul 17, 2026
🤖 Draft PR created: #96424
What it does: Makes
IntegrationSyncFailedMessage.tsxmirrorExportIntegration.tsx— whenhasReasoning(action)is true it wraps the message inReportActionItemMessageWithExplain(which renders the inline "Explain" link and wires up theexplainhandler), and otherwise falls back to the existing muted-text rendering.ActionContentRouter.tsxnow passesoriginalReportthrough so the handler has the report context it needs.Validation
npm run lint-changed— passednpm run typecheck-tsgo— passednpm run react-compiler-compliance-check check <changed files>— passedINTEGRATION_SYNC_FAILEDUI test intests/ui/ReportActionItemTest.tsxexercises the no-reasoning path, which is unchanged (still renders viaReportActionItemBasicMessage), so it remains valid.Please add manual
Tests/QAsteps and mark it Ready for review when it's ready — PullerBear will then assign the reviewer.[-]Explain inline link missing on integration sync failure (`INTEGRATION_SYNC_FAILED`) messages[/-][+][$250] Explain inline link missing on integration sync failure (`INTEGRATION_SYNC_FAILED`) messages[/+]melvin-bot commentedon Jul 19, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022078800561878973179
marcaaron commentedon Jul 20, 2026
PR is in review now.
12 remaining items
melvin-bot commentedon Jul 28, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Jul 28, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Jul 30, 2026
Payment Summary
Contributor+: @mkhutornyi due $250 via NewDot
^ Test case created. Thx
trjExpensify commentedon Aug 3, 2026
approved $250 for @mkhutornyi