Skip to content

[Merge ATS] Handle sync results and offline - #101288

Merged
yuwenmemon merged 12 commits into
Expensify:mainfrom
bernhardoj:feat/99515-handle-sync-results-and-offline
Sep 21, 2026
Merged

yuwenmemon merged 12 commits into
Expensify:mainfrom
bernhardoj:feat/99515-handle-sync-results-and-offline

Conversation

@bernhardoj

@bernhardoj bernhardoj commented Sep 16, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #99515
PROPOSAL:

Tests

Same as QA Steps

  • Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Prerequisite:

  • have mergeATSConnections beta and a control policy
  • Recruiting feature is enabled
  1. Open the recruiting page
  2. Verify the Connect button is disabled while offline
  3. Connect to Greenhouse
  4. Complete the Greenhouse setup
  5. Wait until the syncing is done
  6. Verify a sync result page opens with the number of added, removed, and skipped candidates
  7. Perform sync more than twice and verify that a sync limit modal appears
  8. Press the 3-dot menu
  9. Verify Sync now is disabled while offline
  10. Simulate an auth error by running the code below in the console
Onyx.merge('policy_[your_policy_ID_here]', {
    connections: {
        merge_ats: { 
            lastSync: {
                isAuthenticationError: true,
            },
        },
    },
});
  1. Verify there is no reconnect link button on the error message while offline
  2. Press the 3-dot menu
  3. Verify that Reconnect is disabled while offline

Since syncing takes a long time, to simulate

Syncing completes (steps 5-6):

// run this first
Onyx.merge('policyConnectionSyncProgress_[your_policy_ID_here]'', {
    connectionName: 'merge_ats',
    result: {},
    stageInProgress: 'syncing',
});
// then run
Onyx.merge('policyConnectionSyncProgress_[your_policy_ID_here]', {
    connectionName: 'merge_ats',
    result: {
        addedEmployeesCount: 12,
        removedEmployeesCount: 1,
        skippedEmployees: [{id: 1, name: 'test', reason: 'unknown'}],
    },
    stageInProgress: 'jobDone',
});

Sync limit reached (step 7):

// change the manualSyncTimestamps time to be within 24 hours from your current time
Onyx.merge('policy_[your_policy_ID_here]', {
    connections: {merge_ats: {
        lastSync: {
            manualSyncTimestamps: ['2026-09-18 05:36:00', '2026-09-18 05:36:01']
        },
    }},
});
  • Verify that no errors appear in the JS console

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 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 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)
  • 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.
  • 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
web.mp4

@bernhardoj
bernhardoj requested review from a team as code owners September 16, 2026 06:40
@melvin-bot

melvin-bot Bot commented Sep 16, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx bun ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx bun ./scripts/generateTranslations.ts --compare-ref main

@melvin-bot
melvin-bot Bot requested review from DylanDylann and flaviadefaria and removed request for a team and flaviadefaria September 16, 2026 06:40
@melvin-bot

melvin-bot Bot commented Sep 16, 2026

Copy link
Copy Markdown

@DylanDylann 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 September 16, 2026 06:40
Comment thread src/languages/en.ts
syncResults: {
importedCount: () => ({
one: '1 candidate',
other: (count: number) => `${count} candidates`,

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@yuwenmemon please review this and run the translation script if it looks good

Comment thread src/ROUTES.ts Outdated
Comment thread src/pages/workspace/merge/MergeSyncResultsPageBase.tsx Outdated

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

Copy link
Copy Markdown

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: 83aaa2a84b

ℹ️ 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".

Comment thread src/hooks/useMergeSyncResultsPage.ts
Comment thread src/pages/workspace/merge/MergeSyncResultsPageBase.tsx
policyID={policyID}
featureName={featureName}
policyFeature={CONST.POLICY.POLICY_FEATURE.MORE_FEATURES}
shouldBeBlocked={category === CONST.POLICY.CONNECTIONS.CATEGORY.RECRUITING ? !isBetaEnabled(CONST.BETAS.MERGE_ATS) : false}

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.

let's pass it as param

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Moved it to PAGE_CONFIG

Comment thread src/hooks/useMergeSyncResultsPage.ts Outdated
* screen when the sync reaches the `JOB_DONE` stage with a result payload.
*/
function useHRSyncResultsPage(connectionSyncProgress: OnyxEntry<PolicyConnectionSyncProgress>, isFocused: boolean) {
function useMergeSyncResultsPage(policyID: string) {

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.

The results route is picked from the connection that synced, but the hook now runs on both the HR and the Recruiting page, since both render MergeConnectionsPageBase. The hook only looks at the connection, never at the screen. So when an ATS sync finishes while you're on the HR tab, we navigate to /workspaces//hr/recruiting-sync-results. My suggestion: only navigate when it's correct screen too

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed

@DylanDylann

DylanDylann commented Sep 18, 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

Screen.Recording.2026-09-18.at.18.22.25.mov
Screenshot 2026-09-18 at 18 23 19
Screen.Recording.2026-09-18.at.18.25.00.mov

@DylanDylann

Copy link
Copy Markdown
Contributor

Some above NITs ☝️ The rest looks fine

@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 2d2e07b0..e9773f87 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -8707,6 +8707,12 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
             defaultApprover: 'Standardgenehmiger',
             approverFields: {recruiter: 'Personalvermittler', recruitingCoordinator: 'Recruiting-Koordinator'},
             subtitle: 'Verknüpfen Sie Recruiting-Tools und halten Sie Kandidatengenehmigungen synchron.',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 Kandidat',
+                    other: (count: number) => `${count} Kandidat:innen`,
+                }),
+            },
         },
         merge: {
             connections: 'Verbindungen',
diff --git a/src/languages/el.ts b/src/languages/el.ts
index 7521b1cd..889ecc65 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -7683,6 +7683,12 @@ _Για πιο αναλυτικές οδηγίες, [επισκεφθείτε τ
             defaultApprover: 'Προεπιλεγμένος εγκρίνων',
             approverFields: {recruiter: 'Στρατολογητής', recruitingCoordinator: 'Συντονιστής προσλήψεων'},
             subtitle: 'Συνδέστε τα εργαλεία προσλήψεων και διατηρήστε τις εγκρίσεις υποψηφίων συγχρονισμένες.',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 υποψήφιος',
+                    other: (count: number) => `${count} υποψήφιοι`,
+                }),
+            },
         },
         merge: {
             connections: 'Συνδέσεις',
@@ -7715,8 +7721,8 @@ _Για πιο αναλυτικές οδηγίες, [επισκεφθείτε τ
                 prompt: 'Έχετε φτάσει το όριο συγχρονισμών σας για σήμερα.',
             },
             syncResults: {
-                title: (provider: string) => `Η συγχρονισμός με το ${provider} ολοκληρώθηκε`,
-                successTitle: (provider: string) => `Ο συγχρονισμός της σύνδεσής σας με το ${provider} ολοκληρώθηκε με επιτυχία!`,
+                title: (provider: string) => `ο συγχρονισμός του ${provider} ολοκληρώθηκε`,
+                successTitle: (provider: string) => `Η σύνδεσή σας με το ${provider} συγχρονίστηκε με επιτυχία!`,
                 added: 'Προστέθηκε',
                 removed: 'Αφαιρέθηκε',
                 skipped: 'Παραλείφθηκε',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 45e95a6b..4ae7e8f0 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -7420,6 +7420,12 @@ El plan Controlar empieza en 9 $ por miembro activo al mes.`,
             defaultApprover: 'Aprobador predeterminado',
             approverFields: {recruiter: 'Reclutador', recruitingCoordinator: 'Coordinador de selección'},
             subtitle: 'Conecta herramientas de selección y mantén sincronizadas las aprobaciones de candidatos.',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 candidato',
+                    other: (count: number) => `${count} candidatos`,
+                }),
+            },
         },
         merge: {
             connections: 'Conexiones',
@@ -7450,7 +7456,7 @@ El plan Controlar empieza en 9 $ por miembro activo al mes.`,
             syncLimitReached: {title: 'Inténtalo de nuevo mañana', prompt: 'Has alcanzado tu límite de sincronización de hoy.'},
             syncResults: {
                 title: (provider: string) => `Sincronización de ${provider} completada`,
-                successTitle: (provider: string) => `¡Se sincronizó correctamente tu conexión de ${provider}!`,
+                successTitle: (provider: string) => `¡Se ha sincronizado correctamente tu conexión con ${provider}!`,
                 added: 'Añadido',
                 removed: 'Eliminado',
                 skipped: 'Omitido',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 3b123aa8..292b312c 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -8723,6 +8723,12 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
             defaultApprover: 'Approbateur par défaut',
             approverFields: {recruiter: 'Recruteur', recruitingCoordinator: 'Coordinateur recrutement'},
             subtitle: 'Connectez les outils de recrutement et synchronisez les validations de candidats.',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 candidat',
+                    other: (count: number) => `${count} candidat·s`,
+                }),
+            },
         },
         merge: {
             connections: 'Connexions',
@@ -8753,7 +8759,7 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
             syncLimitReached: {title: 'Réessayez demain', prompt: "Vous avez atteint votre limite de synchronisation pour aujourd'hui."},
             syncResults: {
                 title: (provider: string) => `Synchronisation ${provider} terminée`,
-                successTitle: (provider: string) => `Connexion ${provider} synchronisée avec succès !`,
+                successTitle: (provider: string) => `Connexion à ${provider} synchronisée avec succès !`,
                 added: 'Ajouté',
                 removed: 'Supprimé',
                 skipped: 'Ignoré',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 43a2da2f..f2e536d2 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -8654,6 +8654,12 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
             defaultApprover: 'Approvatore predefinito',
             approverFields: {recruiter: 'Recruiter', recruitingCoordinator: 'Coordinatore recruiting'},
             subtitle: 'Collega gli strumenti di recruiting e mantieni sincronizzate le approvazioni dei candidati.',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 candidato',
+                    other: (count: number) => `${count} candidati`,
+                }),
+            },
         },
         merge: {
             connections: 'Connessioni',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index cf05fc78..039865aa 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -8544,6 +8544,12 @@ ${reportName}`,
             defaultApprover: 'デフォルト承認者',
             approverFields: {recruiter: '採用担当者', recruitingCoordinator: '採用コーディネーター'},
             subtitle: '採用ツールを連携して、候補者の承認を常に同期させます。',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 名の候補者',
+                    other: (count: number) => `${count}件の候補`,
+                }),
+            },
         },
         merge: {
             connections: '接続',
@@ -8574,8 +8580,8 @@ ${reportName}`,
             syncLimitReached: {title: '明日もう一度お試しください', prompt: '本日の同期上限に達しました。'},
             syncResults: {
                 title: (provider: string) => `${provider} の同期が完了しました`,
-                successTitle: (provider: string) => `${provider} との接続が正常に同期されました!`,
-                added: '追加済み',
+                successTitle: (provider: string) => `${provider} の接続が正常に同期されました!`,
+                added: '追加しました',
                 removed: '削除済み',
                 skipped: 'スキップ済み',
             },
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 8698fb6f..08bac0ed 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -8633,6 +8633,12 @@ er bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
             defaultApprover: 'Standaardgoedkeurder',
             approverFields: {recruiter: 'Recruiter', recruitingCoordinator: 'Coördinator werving'},
             subtitle: 'Koppel wervingstools en houd kandidaategoedkeuringen gesynchroniseerd.',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 kandidaat',
+                    other: (count: number) => `${count} kandidaten`,
+                }),
+            },
         },
         merge: {
             connections: 'Verbindingen',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 8568f39f..0ce9b354 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -8651,6 +8651,12 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
             defaultApprover: 'Domyślny zatwierdzający',
             approverFields: {recruiter: 'Rekruter', recruitingCoordinator: 'Koordynator rekrutacji'},
             subtitle: 'Połącz narzędzia rekrutacyjne i utrzymuj zgody kandydatów w synchronizacji.',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 kandydat',
+                    other: (count: number) => `${count} kandydatów`,
+                }),
+            },
         },
         merge: {
             connections: 'Połączenia',
@@ -8680,7 +8686,7 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
             syncingModalDescription: 'Pierwsze połączenie może chwilę potrwać. Zostaniesz powiadomiony o wszelkich błędach.',
             syncLimitReached: {title: 'Spróbuj ponownie jutro', prompt: 'Osiągnąłeś dzienny limit synchronizacji.'},
             syncResults: {
-                title: (provider: string) => `Synchronizacja z ${provider} zakończona`,
+                title: (provider: string) => `Zsynchronizowano z ${provider}`,
                 successTitle: (provider: string) => `Pomyślnie zsynchronizowano twoje połączenie z ${provider}!`,
                 added: 'Dodano',
                 removed: 'Usunięto',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 11035d3c..8bbb21cd 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -8636,6 +8636,12 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
             defaultApprover: 'Aprovador padrão',
             approverFields: {recruiter: 'Recrutador', recruitingCoordinator: 'Coordenador de recrutamento'},
             subtitle: 'Conecte ferramentas de recrutamento e mantenha as aprovações de candidatos em sincronia.',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 candidato',
+                    other: (count: number) => `${count} candidatos`,
+                }),
+            },
         },
         merge: {
             connections: 'Conexões',
@@ -8666,7 +8672,7 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
             syncLimitReached: {title: 'Tente novamente amanhã', prompt: 'Você atingiu o limite de sincronizações de hoje.'},
             syncResults: {
                 title: (provider: string) => `Sincronização com ${provider} concluída`,
-                successTitle: (provider: string) => `Conexão com ${provider} sincronizada com sucesso!`,
+                successTitle: (provider: string) => `Conexão com o ${provider} sincronizada com sucesso!`,
                 added: 'Adicionado',
                 removed: 'Removido',
                 skipped: 'Ignorado',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 4ffcf8fa..e02ead70 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -8323,6 +8323,12 @@ ${reportName}`,
             defaultApprover: '默认审批人',
             approverFields: {recruiter: '招聘人员', recruitingCoordinator: '招聘协调员'},
             subtitle: '连接招聘工具并保持候选人审批同步。',
+            syncResults: {
+                importedCount: () => ({
+                    one: '1 名候选人',
+                    other: (count: number) => `${count} 名候选人`,
+                }),
+            },
         },
         merge: {
             connections: '连接',

Note

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

View workflow run

@codecov

codecov Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/ROUTES.ts 29.19% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 62.50% <ø> (ø)
src/pages/workspace/WorkspaceMembersPage.tsx 73.30% <ø> (ø)
src/pages/workspace/hr/WorkspaceHRPage.tsx 0.00% <ø> (ø)
src/hooks/useMergeSyncResultsPage.ts 96.87% <96.87%> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 5.96% <0.00%> (-0.01%) ⬇️
...rc/pages/workspace/hr/DynamicHRSyncResultsPage.tsx 0.00% <0.00%> (ø)
src/pages/workspace/merge/MergeProviderCard.tsx 0.00% <0.00%> (ø)
...pages/workspace/merge/MergeSyncResultsListener.tsx 0.00% <0.00%> (ø)
... and 4 more
... and 10 files with indirect coverage changes

@DylanDylann

Copy link
Copy Markdown
Contributor

@codex review

@melvin-bot
melvin-bot Bot requested a review from yuwenmemon September 21, 2026 11:29
@yuwenmemon
yuwenmemon merged commit 317528c into Expensify:main Sep 21, 2026
36 of 38 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 yuwenmemon 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.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/yuwenmemon in version: 9.4.92-0 🚀

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

@izarutskaya

izarutskaya commented Sep 23, 2026 •

Copy link
Copy Markdown

@bernhardoj We are blocked with Greenhouse, as don't have credentials. We were trying with snippet, but it doesn't work for step 7 It is completed in Web only with different snippet and it's passed

1790198814546.101288-Web.mp4

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.4.92-8 🚀

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

Bundle Size Analysis (Sentry):

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