Skip to content

[Payment due @Ollyws] Display recurrence count for de-duplicated sync failure messages#88008

Merged
tylerkaraszewski merged 6 commits intomainfrom
yuwen-dedup-sync-failed-app
Apr 21, 2026
Merged

[Payment due @Ollyws] Display recurrence count for de-duplicated sync failure messages#88008
tylerkaraszewski merged 6 commits intomainfrom
yuwen-dedup-sync-failed-app

Conversation

@yuwenmemon
Copy link
Copy Markdown
Contributor

@yuwenmemon yuwenmemon commented Apr 15, 2026

Explanation of Change

When the Auth service de-duplicates consecutive identical INTEGRATIONSYNCFAILED messages in #admins rooms, it adds a recurrenceCount field to the message's originalMessage. This PR updates the App frontend to read that field and display "This issue has recurred X times." after the sync failure text.

Changes:

  • Added recurrenceCount to OriginalMessageIntegrationSyncFailed type
  • Updated getIntegrationSyncFailedMessage to append recurrence text when recurrenceCount > 1
  • Added integrationSyncFailedRecurrence translation key to all language files

Fixed Issues

For https://github.com/Expensify/Expensify/issues/624351

Tests

  • None this will be tested with Auth after the recurrence logic is merged

Offline tests

N/A - this is server-rendered content, offline behavior unchanged.

QA Steps

  • None this will be tested with Auth after the recurrence logic is merged

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 steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover 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 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)
    • 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
      • 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:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • 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.å
    • 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
  • 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)
  • 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
  • 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 new assets were added or existing ones were modified, I verified that:
    • 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.
  • 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.
  • 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.
  • 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

MacOS: Chrome / Safari

Tested locally — message updates in place with recurrence count text after de-duplication.

@yuwenmemon yuwenmemon requested review from a team as code owners April 15, 2026 21:51
@melvin-bot melvin-bot Bot requested review from a team, heyjennahay and ikevin127 and removed request for a team April 15, 2026 21:51
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 15, 2026

@ikevin127 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 requested a review from Ollyws April 15, 2026 21:51
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 15, 2026

@Ollyws 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 April 15, 2026 21:51
@OSBotify

This comment has been minimized.

Comment thread src/languages/de.ts Outdated
takeControl: `Kontrolle übernommen`,
integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
`Beim Synchronisieren mit ${label}${errorMessage ? ` ("${errorMessage}")` : ''} ist ein Problem aufgetreten. Bitte behebe das Problem in den <a href="${workspaceAccountingLink}">Workspace-Einstellungen</a>.`,
integrationSyncFailedRecurrence: ({count}: {count: number}) => `This issue has recurred ${count} times.`,
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.

❌ CONSISTENCY-3 (docs)

The string This issue has recurred ${count} times. is in English, not German. The same untranslated English string is copy-pasted across 7 non-English locale files (de, fr, it, ja, nl, pl, pt-BR, zh-hans), which is both a duplication issue and an i18n defect. Only es.ts has an actual translation.

Provide a proper German translation, e.g.:

integrationSyncFailedRecurrence: ({count}: {count: number}) => `Dieses Problem ist ${count} Mal aufgetreten.`,

Reviewed at: c00f999 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Comment thread src/languages/fr.ts Outdated
takeControl: `a pris le contrôle`,
integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
`un problème est survenu lors de la synchronisation avec ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Veuillez corriger le problème dans les <a href="${workspaceAccountingLink}">paramètres de l’espace de travail</a>.`,
integrationSyncFailedRecurrence: ({count}: {count: number}) => `This issue has recurred ${count} times.`,
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.

❌ CONSISTENCY-3 (docs)

The string This issue has recurred ${count} times. is in English, not French. This is the same untranslated English string duplicated across all non-English locale files (except es.ts).

Provide a proper French translation, e.g.:

integrationSyncFailedRecurrence: ({count}: {count: number}) => `Ce problème s'est reproduit ${count} fois.`,

Reviewed at: c00f999 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Comment thread src/languages/it.ts Outdated
takeControl: `ha preso il controllo`,
integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
`si è verificato un problema di sincronizzazione con ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Risolvi il problema nelle <a href="${workspaceAccountingLink}">impostazioni dello spazio di lavoro</a>.`,
integrationSyncFailedRecurrence: ({count}: {count: number}) => `This issue has recurred ${count} times.`,
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.

❌ CONSISTENCY-3 (docs)

The string This issue has recurred ${count} times. is in English, not Italian. This is the same untranslated English string duplicated across all non-English locale files (except es.ts).

Provide a proper Italian translation, e.g.:

integrationSyncFailedRecurrence: ({count}: {count: number}) => `Questo problema si è verificato ${count} volte.`,

Reviewed at: c00f999 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Comment thread src/languages/ja.ts Outdated
takeControl: `管理権限を取得しました`,
integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
`${label}${errorMessage ? ` ("${errorMessage}")` : ''}との同期中に問題が発生しました。<a href="${workspaceAccountingLink}">ワークスペース設定</a>で問題を解決してください。`,
integrationSyncFailedRecurrence: ({count}: {count: number}) => `This issue has recurred ${count} times.`,
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.

❌ CONSISTENCY-3 (docs)

The string This issue has recurred ${count} times. is in English, not Japanese. This is the same untranslated English string duplicated across all non-English locale files (except es.ts).

Provide a proper Japanese translation, e.g.:

integrationSyncFailedRecurrence: ({count}: {count: number}) => `この問題は${count}回発生しています。`,

Reviewed at: c00f999 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Comment thread src/languages/nl.ts Outdated
takeControl: `nam de controle over`,
integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
`er trad een probleem op bij het synchroniseren met ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Los het probleem op in de <a href="${workspaceAccountingLink}">werkruimte-instellingen</a>.`,
integrationSyncFailedRecurrence: ({count}: {count: number}) => `This issue has recurred ${count} times.`,
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.

❌ CONSISTENCY-3 (docs)

The string This issue has recurred ${count} times. is in English, not Dutch. This is the same untranslated English string duplicated across all non-English locale files (except es.ts).

Provide a proper Dutch translation, e.g.:

integrationSyncFailedRecurrence: ({count}: {count: number}) => `Dit probleem is ${count} keer opgetreden.`,

Reviewed at: c00f999 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Comment thread src/languages/pl.ts Outdated
takeControl: `przejął kontrolę`,
integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
`wystąpił problem z synchronizacją z ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Napraw problem w <a href="${workspaceAccountingLink}">ustawieniach przestrzeni roboczej</a>.`,
integrationSyncFailedRecurrence: ({count}: {count: number}) => `This issue has recurred ${count} times.`,
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.

❌ CONSISTENCY-3 (docs)

The string This issue has recurred ${count} times. is in English, not Polish. This is the same untranslated English string duplicated across all non-English locale files (except es.ts).

Provide a proper Polish translation, e.g.:

integrationSyncFailedRecurrence: ({count}: {count: number}) => `Ten problem wystąpił ${count} razy.`,

Reviewed at: c00f999 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Comment thread src/languages/pt-BR.ts Outdated
takeControl: `assumiu o controle`,
integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
`houve um problema ao sincronizar com ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Corrija o problema em <a href="${workspaceAccountingLink}">configurações do workspace</a>.`,
integrationSyncFailedRecurrence: ({count}: {count: number}) => `This issue has recurred ${count} times.`,
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.

❌ CONSISTENCY-3 (docs)

The string This issue has recurred ${count} times. is in English, not Portuguese. This is the same untranslated English string duplicated across all non-English locale files (except es.ts).

Provide a proper Portuguese translation, e.g.:

integrationSyncFailedRecurrence: ({count}: {count: number}) => `Este problema ocorreu ${count} vezes.`,

Reviewed at: c00f999 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Comment thread src/languages/zh-hans.ts Outdated
takeControl: `取得控制权`,
integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
`与 ${label}${errorMessage ? ` ("${errorMessage}")` : ''} 同步时出现问题。请在<a href="${workspaceAccountingLink}">工作区设置</a>中修复此问题。`,
integrationSyncFailedRecurrence: ({count}: {count: number}) => `This issue has recurred ${count} times.`,
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.

❌ CONSISTENCY-3 (docs)

The string This issue has recurred ${count} times. is in English, not Chinese. This is the same untranslated English string duplicated across all non-English locale files (except es.ts).

Provide a proper Simplified Chinese translation, e.g.:

integrationSyncFailedRecurrence: ({count}: {count: number}) => `此问题已重复发生${count}次。`,

Reviewed at: c00f999 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

@OSBotify
Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 50276d50..dc9d0097 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7860,7 +7860,7 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
                 takeControl: `Kontrolle übernommen`,
                 integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
                     `Beim Synchronisieren mit ${label}${errorMessage ? ` ("${errorMessage}")` : ''} ist ein Problem aufgetreten. Bitte behebe das Problem in den <a href="${workspaceAccountingLink}">Workspace-Einstellungen</a>.`,
-                integrationSyncFailedRecurrence: ({count}: {count: number}) => `Dieses Problem ist ${count} Mal erneut aufgetreten.`,
+                integrationSyncFailedRecurrence: ({count}: {count: number}) => `(${count} Mal wiederholt.)`,
                 companyCardConnectionBroken: ({feedName, workspaceCompanyCardRoute}: {feedName: string; workspaceCompanyCardRoute: string}) =>
                     `Die Verbindung für ${feedName} ist unterbrochen. Um Kartenimporte wiederherzustellen, <a href='${workspaceCompanyCardRoute}'>melden Sie sich bei Ihrer Bank an</a>.`,
                 plaidBalanceFailure: ({maskedAccountNumber, walletRoute}: {maskedAccountNumber: string; walletRoute: string}) =>
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index d34bb439..c19a70d4 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7882,7 +7882,7 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
                 takeControl: `a pris le contrôle`,
                 integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
                     `un problème est survenu lors de la synchronisation avec ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Veuillez corriger le problème dans les <a href="${workspaceAccountingLink}">paramètres de l’espace de travail</a>.`,
-                integrationSyncFailedRecurrence: ({count}: {count: number}) => `Ce problème s’est reproduit ${count} fois.`,
+                integrationSyncFailedRecurrence: ({count}: {count: number}) => `(Répété ${count} fois.)`,
                 companyCardConnectionBroken: ({feedName, workspaceCompanyCardRoute}: {feedName: string; workspaceCompanyCardRoute: string}) =>
                     `La connexion ${feedName} est interrompue. Pour rétablir l’importation des cartes, <a href=’${workspaceCompanyCardRoute}’>connectez-vous à votre banque</a>.`,
                 plaidBalanceFailure: ({maskedAccountNumber, walletRoute}: {maskedAccountNumber: string; walletRoute: string}) =>
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 3e328956..cbb1185b 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -7848,7 +7848,7 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
                 takeControl: `ha preso il controllo`,
                 integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
                     `si è verificato un problema di sincronizzazione con ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Risolvi il problema nelle <a href="${workspaceAccountingLink}">impostazioni dello spazio di lavoro</a>.`,
-                integrationSyncFailedRecurrence: ({count}: {count: number}) => `Questo problema si è ripresentato ${count} volte.`,
+                integrationSyncFailedRecurrence: ({count}: {count: number}) => `(Ripetuto ${count} volte.)`,
                 companyCardConnectionBroken: ({feedName, workspaceCompanyCardRoute}: {feedName: string; workspaceCompanyCardRoute: string}) =>
                     `La connessione ${feedName} è interrotta. Per ripristinare le importazioni della carta, <a href='${workspaceCompanyCardRoute}'>accedi alla tua banca</a>.`,
                 plaidBalanceFailure: ({maskedAccountNumber, walletRoute}: {maskedAccountNumber: string; walletRoute: string}) =>
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index e7e39243..015c2100 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -7751,7 +7751,7 @@ ${reportName}
                 takeControl: `管理権限を取得しました`,
                 integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
                     `${label}${errorMessage ? ` ("${errorMessage}")` : ''}との同期中に問題が発生しました。<a href="${workspaceAccountingLink}">ワークスペース設定</a>で問題を解決してください。`,
-                integrationSyncFailedRecurrence: ({count}: {count: number}) => `この問題は${count}回再発しています。`,
+                integrationSyncFailedRecurrence: ({count}: {count: number}) => `(${count} 回繰り返し)`,
                 companyCardConnectionBroken: ({feedName, workspaceCompanyCardRoute}: {feedName: string; workspaceCompanyCardRoute: string}) =>
                     `${feedName} との接続が切断されています。カードの取引明細の取込を再開するには、<a href='${workspaceCompanyCardRoute}'>銀行にログイン</a>してください。`,
                 plaidBalanceFailure: ({maskedAccountNumber, walletRoute}: {maskedAccountNumber: string; walletRoute: string}) =>
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 93507e83..c2605d61 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -7825,7 +7825,7 @@ Voeg meer bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
                 takeControl: `nam de controle over`,
                 integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
                     `er trad een probleem op bij het synchroniseren met ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Los het probleem op in de <a href="${workspaceAccountingLink}">werkruimte-instellingen</a>.`,
-                integrationSyncFailedRecurrence: ({count}: {count: number}) => `Dit probleem is ${count} keer opnieuw opgetreden.`,
+                integrationSyncFailedRecurrence: ({count}: {count: number}) => `(${count} keer herhaald.)`,
                 companyCardConnectionBroken: ({feedName, workspaceCompanyCardRoute}: {feedName: string; workspaceCompanyCardRoute: string}) =>
                     `De verbinding met ${feedName} is verbroken. <a href='${workspaceCompanyCardRoute}'>Log in bij je bank</a> om kaartimports te herstellen.`,
                 plaidBalanceFailure: ({maskedAccountNumber, walletRoute}: {maskedAccountNumber: string; walletRoute: string}) =>
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 1577ef1c..e50e27a6 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -7814,7 +7814,7 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
                 takeControl: `przejął kontrolę`,
                 integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
                     `wystąpił problem z synchronizacją z ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Napraw problem w <a href="${workspaceAccountingLink}">ustawieniach przestrzeni roboczej</a>.`,
-                integrationSyncFailedRecurrence: ({count}: {count: number}) => `Ten problem wystąpił ponownie ${count} razy.`,
+                integrationSyncFailedRecurrence: ({count}: {count: number}) => `(Powtórzono ${count} razy.)`,
                 companyCardConnectionBroken: ({feedName, workspaceCompanyCardRoute}: {feedName: string; workspaceCompanyCardRoute: string}) =>
                     `Połączenie ${feedName} jest przerwane. Aby przywrócić importy kart, <a href='${workspaceCompanyCardRoute}'>zaloguj się do swojego banku</a>.`,
                 plaidBalanceFailure: ({maskedAccountNumber, walletRoute}: {maskedAccountNumber: string; walletRoute: string}) =>
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 18723ab1..e55ed3f6 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -7818,7 +7818,7 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
                 takeControl: `assumiu o controle`,
                 integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
                     `houve um problema ao sincronizar com ${label}${errorMessage ? ` ("${errorMessage}")` : ''}. Corrija o problema em <a href="${workspaceAccountingLink}">configurações do workspace</a>.`,
-                integrationSyncFailedRecurrence: ({count}: {count: number}) => `Este problema voltou a ocorrer ${count} vezes.`,
+                integrationSyncFailedRecurrence: ({count}: {count: number}) => `(Repetido ${count} vezes.)`,
                 companyCardConnectionBroken: ({feedName, workspaceCompanyCardRoute}: {feedName: string; workspaceCompanyCardRoute: string}) =>
                     `A conexão de ${feedName} está interrompida. Para restaurar as importações do cartão, <a href='${workspaceCompanyCardRoute}'>faça login no seu banco</a>.`,
                 plaidBalanceFailure: ({maskedAccountNumber, walletRoute}: {maskedAccountNumber: string; walletRoute: string}) =>
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index b5f41e98..e375a520 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -7614,7 +7614,7 @@ ${reportName}
                 takeControl: `取得控制权`,
                 integrationSyncFailed: (label: string, errorMessage: string, workspaceAccountingLink?: string) =>
                     `与 ${label}${errorMessage ? ` ("${errorMessage}")` : ''} 同步时出现问题。请在<a href="${workspaceAccountingLink}">工作区设置</a>中修复此问题。`,
-                integrationSyncFailedRecurrence: ({count}: {count: number}) => `此问题已重复出现 ${count} 次。`,
+                integrationSyncFailedRecurrence: ({count}: {count: number}) => `(重复 ${count} 次。)`,
                 companyCardConnectionBroken: ({feedName, workspaceCompanyCardRoute}: {feedName: string; workspaceCompanyCardRoute: string}) =>
                     `${feedName} 连接已中断。要恢复银行卡导入,请<a href='${workspaceCompanyCardRoute}'>登录您的银行账户</a>。`,
                 plaidBalanceFailure: ({maskedAccountNumber, walletRoute}: {maskedAccountNumber: string; walletRoute: string}) =>

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c00f9998e1

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/languages/fr.ts Outdated
integrationSyncFailedRecurrence: ({count}: {count: number}) => `This issue has recurred ${count} times.`,
companyCardConnectionBroken: ({feedName, workspaceCompanyCardRoute}: {feedName: string; workspaceCompanyCardRoute: string}) =>
`La connexion ${feedName} est interrompue. Pour rétablir l’importation des cartes, <a href='${workspaceCompanyCardRoute}'>connectez-vous à votre banque</a>.`,
`La connexion ${feedName} est interrompue. Pour rétablir l’importation des cartes, <a href=${workspaceCompanyCardRoute}>connectez-vous à votre banque</a>.`,
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Restore ASCII quotes in French company-card link

The French companyCardConnectionBroken translation now uses typographic apostrophes around href (’...’) instead of valid HTML quote characters. In notifications rendered from this string, the anchor can fail to parse as a link, so French users may not be able to click through to reconnect their bank from this message.

Useful? React with 👍 / 👎.

yuwenmemon and others added 4 commits April 15, 2026 15:20
Add client-side rendering of recurrenceCount for INTEGRATIONSYNCFAILED
messages that have been de-duplicated by the server.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@yuwenmemon yuwenmemon force-pushed the yuwen-dedup-sync-failed-app branch from bbe5b35 to ad8a897 Compare April 15, 2026 22:23
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 15, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/libs/ReportActionsUtils.ts 76.75% <100.00%> (+0.03%) ⬆️
... and 29 files with indirect coverage changes

@ikevin127
Copy link
Copy Markdown
Contributor

@yuwenmemon Who's supposed to review this ? I'm seeing @Ollyws assigned, happy to have them review 🙌

@yuwenmemon
Copy link
Copy Markdown
Contributor Author

Yeah dunno why it assigned two... Will remove your assignment @ikevin127

@yuwenmemon yuwenmemon removed the request for review from ikevin127 April 15, 2026 22:41
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Ollyws
Copy link
Copy Markdown
Contributor

Ollyws commented Apr 16, 2026

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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • 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.
    • 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
  • 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)
  • 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
  • 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.
  • 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.
  • 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 Android_Native
Android: mWeb Chrome Android_Chrome
iOS: HybridApp iOS_Native
iOS: mWeb Safari iOS_Safari
MacOS: Chrome / Safari MacOS_Chrome

Copy link
Copy Markdown
Contributor

@Ollyws Ollyws left a comment

Choose a reason for hiding this comment

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

I don't know if the backend changes are live yet, so I just hard coded the recurrenceCount but LGTM.

@melvin-bot melvin-bot Bot requested a review from tylerkaraszewski April 16, 2026 12:26
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 16, 2026

@tylerkaraszewski 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 Display recurrence count for de-duplicated sync failure messages [Payment due @Ollyws] Display recurrence count for de-duplicated sync failure messages Apr 16, 2026
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 16, 2026

🎯 @Ollyws, 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 - no internal issue.

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.

@tylerkaraszewski
Copy link
Copy Markdown
Contributor

Tests are failing

# Conflicts:
#	tests/unit/ReportActionsUtilsTest.ts
@yuwenmemon
Copy link
Copy Markdown
Contributor Author

@tylerkaraszewski updated!

@tylerkaraszewski tylerkaraszewski merged commit 7d73cd8 into main Apr 21, 2026
37 checks passed
@tylerkaraszewski tylerkaraszewski deleted the yuwen-dedup-sync-failed-app branch April 21, 2026 22:19
@github-actions
Copy link
Copy Markdown
Contributor

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

@OSBotify
Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

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.

5 participants