ECHO-437 Transcription status update when in progress

[ussaama]

Summary by CodeRabbit

• New Features

  • Clearer transcript status: shows “Transcription in progress…” while processing and “Transcript not available” when an error occurs.
  • Improved chunk handling to surface transcription errors in the UI.

• Chores

  • Added translations for the new status message across English, German, Spanish, French, and Dutch.
  • Updated localization references to reflect minor source shifts without changing existing translations.
  • Minor localization polish, including an added translation for “Speaker” in French.

[linear]

ECHO-437 Change text when audio is being processed for transcript

[coderabbitai]

Walkthrough

Adds optional error field to conversation chunk type and fetch logic, updates ConversationChunkAudioTranscript to show “Transcription in progress…” vs “Transcript not available” based on error/transcript presence, wires error through ProjectConversationTranscript, and updates locale catalogs with the new string and shifted references.

Changes

Cohort / File(s)	Summary
Conversation transcript UI echo/frontend/src/components/conversation/ConversationChunkAudioTranscript.tsx, echo/frontend/src/routes/project/conversation/ProjectConversationTranscript.tsx	Component now accepts chunk.error and conditionally renders “Transcription in progress…” when no transcript and no error, otherwise “Transcript not available”; ProjectConversationTranscript passes error through (chunk.error ?? "").
Data fetching hooks echo/frontend/src/components/conversation/hooks/index.ts	Extends Directus readItems fields to include "error"; no control-flow changes.
Types echo/frontend/src/lib/types.d.ts	Adds optional error?: string | null to TConversationChunk.
Locales (.po) echo/frontend/src/locales/en-US.po, .../de-DE.po, .../es-ES.po, .../fr-FR.po, .../nl-NL.po	Adds translation entry for “Transcription in progress…”. Updates source references/line numbers; no semantic changes to existing strings.
Locales (.ts) echo/frontend/src/locales/en-US.ts, .../de-DE.ts, .../es-ES.ts, .../nl-NL.ts	No functional changes; formatting/no-op diffs.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• ECHO-376 optimize conversation related queries #260 — Also adjusts conversation chunk field selection and related components; this PR adds error on top of similar shaping.
• bugfixes and minor refactoring #91 — Touches ConversationChunkAudioTranscript logic; related to how audio/transcript rendering is handled.

Suggested labels

improvement

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "ECHO-437 Transcription status update when in progress" succinctly names the issue and the primary change (showing transcription status while audio is processed), and it maps directly to the changes that add the "Transcription in progress…" message and related type/field updates; it is concise and readable for history scanning. LGTM.
Linked Issues Check	✅ Passed	The patch satisfies the core objectives of [ECHO-437] by adding an optional chunk.error field (types and data fetch), passing that field into ConversationChunkAudioTranscript, and switching the UI to render "Transcription in progress…" when no error is present instead of always showing "Transcript not available," which addresses the user confusion about in-flight transcriptions. This will surface processing state for uploads/retranscriptions provided the backend semantics treat absence of an error as "processing." Verify backend behavior and add tests to ensure retranscription/upload flows leave chunk.error unset during processing and set it on failure.
Out of Scope Changes Check	✅ Passed	All modified files are directly related to the transcription-status objective: types, the Directus fields in the hook, the component prop handling, the ProjectConversationTranscript mapping, and the new localized strings; locale reference/line shifts and a trailing newline are innocuous. I see no unrelated feature work or refactors introduced in this changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch transcription-status

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 7

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (10)

echo/frontend/src/lib/types.d.ts (1)

82-91: Unify chunk typing with runtime usage (timestamp/path/error).

UI treats timestamp as a string and uses path + error; types currently miss path and force Date. Align to avoid drift and invalid Date edge cases.

Apply:

 type TConversationChunk = {
   id: string;
   created_at: Date;
   updated_at: Date;
   conversation_id: string;

   transcript?: string;
-  timestamp: Date;
+  // Directus returns ISO strings; UI passes strings to Date()
+  timestamp: string;
+  // Used to decide whether to render audio player
+  path?: string;
   error?: string | null;
 };

echo/frontend/src/components/conversation/hooks/index.ts (1)

47-66: Type the chunks fetch and include path/error explicitly.

Good call adding error. Let’s type the response to catch schema drifts at compile time.

-      const response = await directus.request(
-        readItems("conversation_chunk", {
+      const response = await directus.request<TConversationChunk[]>(
+        readItems("conversation_chunk", {
           filter: {
             conversation_id: {
               _eq: conversationId,
             },
           },
           sort: ["timestamp"],
           limit: initialLimit,
           offset: pageParam * initialLimit,
-          fields: ["id", "conversation_id", "transcript", "path", "timestamp", "error"],
+          fields: ["id","conversation_id","transcript","path","timestamp","error"],
         }),
       );

Also applies to: 60-61

echo/frontend/src/routes/project/conversation/ProjectConversationTranscript.tsx (2)

298-309: Show “in progress” state when there are zero chunks but processing isn’t finished (matches ECHO‑437).

Right now zero chunks => “No Transcript Available,” which implies failure. If audio/transcription is still running, surface a progress state instead.

-          {allChunks.length === 0 ? (
-            <Alert
-              icon={<IconAlertCircle size={16} />}
-              title={t`No Transcript Available`}
-              color="gray"
-            >
-              <Trans>
-                No transcript exists for this conversation yet. Please check
-                back later.
-              </Trans>
-            </Alert>
-          ) : (
+          {allChunks.length === 0 ? (
+            (conversationQuery.data &&
+              (!conversationQuery.data.is_audio_processing_finished ||
+               !conversationQuery.data.is_all_chunks_transcribed)) ? (
+              <Alert
+                icon={<IconAlertCircle size={16} />}
+                title={t`Processing Transcript`}
+                color="gray"
+              >
+                <Trans>
+                  The transcript for this conversation is being processed. Please
+                  check back later.
+                </Trans>
+              </Alert>
+            ) : (
+              <Alert
+                icon={<IconAlertCircle size={16} />}
+                title={t`No Transcript Available`}
+                color="gray"
+              >
+                <Trans>
+                  No transcript exists for this conversation yet. Please check
+                  back later.
+                </Trans>
+              </Alert>
+            )
+          ) : (

---

326-334: Avoid passing an empty string for timestamp/error; keep types faithful.

An empty timestamp becomes Invalid Date in the child; prefer passing actual values and letting the child guard. Also, if you adopt the types.d.ts change, these line types will align.

                   <ConversationChunkAudioTranscript
                     chunk={{
                       conversation_id: chunk.conversation_id as string,
                       id: chunk.id,
                       path: chunk.path ?? "",
-                      timestamp: chunk.timestamp ?? "",
-                      transcript: chunk.transcript ?? "",
-                      error: chunk.error ?? "",
+                      timestamp: chunk.timestamp as any,
+                      transcript: chunk.transcript ?? "",
+                      error: chunk.error ?? null,
                     }}
                     showAudioPlayer={showAudioPlayer}
                   />

echo/frontend/src/components/conversation/ConversationChunkAudioTranscript.tsx (1)

11-18: Harden timestamp rendering and localize missing strings.

• Guard against invalid Date; render time only when available.
• Localize “Submitted via text input” and the audio‑load failure message.
• Align prop typing with actual usage (string | Date) to stop cast churn.

   chunk: {
     conversation_id: string;
     id: string;
     path: string;
-    timestamp: string;
+    timestamp: string | Date;
     transcript: string;
-    error?: string | null;
+    error?: string | null;
   };
@@
-        <span className="text-sm">
-          {new Date(chunk.timestamp).toLocaleTimeString()}
-        </span>
+        <span className="text-sm">
+          {chunk.timestamp ? new Date(chunk.timestamp).toLocaleTimeString() : null}
+        </span>
@@
-            {!chunk.path ? (
-              <Text size="xs" className="px-2" color="gray">
-                Submitted via text input
-              </Text>
+            {!chunk.path ? (
+              <Text size="xs" className="px-2" color="gray">
+                {t`Submitted via text input`}
+              </Text>
             ) : audioUrlQuery.isLoading ? (
               <Skeleton height={36} width="100%" />
             ) : audioUrlQuery.isError ? (
-              <Text size="xs" c="gray">
-                Failed to load audio or the audio is not available
-              </Text>
+              <Text size="xs" c="gray">
+                {t`Failed to load audio or the audio is not available`}
+              </Text>
             ) : (
@@
-        ) : chunk.error ? (
+        ) : chunk.error ? (
           <span className="italic text-gray-500">{t`Transcript not available`}</span>
-        ) : (
+        ) : (
           <span className="italic text-gray-500">{t`Transcription in progress…`}</span>
         )}

Also applies to: 31-33, 41-48, 64-70

echo/frontend/src/locales/fr-FR.po (1)

2240-2246: Use “étiquettes” instead of “tags” for consistency

Elsewhere “Tags” → “Étiquettes”. Align search label.

-msgid "Search tags"
-msgstr "Rechercher des tags"
+msgid "Search tags"
+msgstr "Rechercher des étiquettes"

echo/frontend/src/locales/es-ES.po (4)

539-543: Mistranslation: “Confirm Publishing” ≠ “Publicar”

Button should indicate confirmation, not the action itself.

-msgid "Confirm Publishing"
-msgstr "Publicar"
+msgid "Confirm Publishing"
+msgstr "Confirmar publicación"

---

948-949: Spanish grammar fix

Leftover English: “conversation”. Use “conversación” and match gender with “nueva”.

-msgid "Enter a name for the new conversation"
-msgstr "Ingresa un nombre para el nuevo conversation"
+msgid "Enter a name for the new conversation"
+msgstr "Ingresa un nombre para la nueva conversación"

---

3059-3062: “Yes” button translated as “Detener”

This is likely a copy/paste error. Should be “Sí”.

-msgid "participant.button.stop.yes"
-msgstr "Detener"
+msgid "participant.button.stop.yes"
+msgstr "Sí"

---

1556-1563: Fix Spanish labels for stop modal buttons

Both stop.* entries in echo/frontend/src/locales/es-ES.po are wrong — they use "Detener". Update to match finish.*:

• participant.button.stop.no (≈line 1557): msgstr "Detener" → "No"
• participant.button.stop.yes (≈line 3060): msgstr "Detener" → "Sí"

participant.button.finish.no.text.mode (≈1562 = "No") and participant.button.finish.yes.text.mode (≈3065 = "Sí") are correct. LGTM after fix.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 67a5e0f and 4d78d88.

📒 Files selected for processing (13)

• echo/frontend/src/components/conversation/ConversationChunkAudioTranscript.tsx (2 hunks)
• echo/frontend/src/components/conversation/hooks/index.ts (1 hunks)
• echo/frontend/src/lib/types.d.ts (1 hunks)
• echo/frontend/src/locales/de-DE.po (11 hunks)
• echo/frontend/src/locales/de-DE.ts (1 hunks)
• echo/frontend/src/locales/en-US.po (11 hunks)
• echo/frontend/src/locales/en-US.ts (1 hunks)
• echo/frontend/src/locales/es-ES.po (11 hunks)
• echo/frontend/src/locales/es-ES.ts (1 hunks)
• echo/frontend/src/locales/fr-FR.po (11 hunks)
• echo/frontend/src/locales/nl-NL.po (11 hunks)
• echo/frontend/src/locales/nl-NL.ts (1 hunks)
• echo/frontend/src/routes/project/conversation/ProjectConversationTranscript.tsx (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (2)

echo/frontend/src/locales/nl-NL.ts (4)

echo/frontend/src/locales/de-DE.ts (1)

• messages (1-1)

echo/frontend/src/locales/en-US.ts (1)

• messages (1-1)

echo/frontend/src/locales/es-ES.ts (1)

• messages (1-1)

echo/frontend/src/locales/fr-FR.ts (1)

• messages (1-1)

echo/frontend/src/locales/de-DE.ts (1)

echo/frontend/src/locales/en-US.ts (1)

• messages (1-1)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: ci-check-server

🔇 Additional comments (11)

echo/frontend/src/locales/de-DE.ts (1)

1-1: LGTM: New in-progress copy present and accurate.

"Transkription läuft…" is included and reads well in German for the intended status. Ship it.

echo/frontend/src/locales/es-ES.ts (1)

1-1: Locales: Spanish string for “Transcription in progress…” present — LGTM

Key and translation exist; consistent with the new UI flow.

Please confirm PO catalogs were updated and compiled so the new key resolves at runtime across environments.

echo/frontend/src/locales/nl-NL.ts (1)

1-1: Locales: Dutch string for “Transcription in progress…” present — LGTM

The new status string is covered. Minor: ensure both this and any legacy “in progress” variants aren’t conflicting in the component usage.

Can you confirm the component uses the ellipsis variant key everywhere (hash ending with 0l9syB) so we don’t show mixed copy?

echo/frontend/src/locales/en-US.ts (1)

1-1: Locales: Base string added — LGTM

EN source includes “Transcription in progress…” as expected.

echo/frontend/src/components/conversation/ConversationChunkAudioTranscript.tsx (1)

63-71: Per‑chunk status logic — LGTM

The error‑aware fallback vs. in‑progress message is clean and matches the product brief.

echo/frontend/src/locales/en-US.po (1)

638-641: LGTM on ref shifts and unchanged strings

Reference updates and unchanged copy look solid. No action needed.

Also applies to: 1767-1771, 2205-2208, 2280-2283, 2297-2300, 2528-2531, 2849-2852

echo/frontend/src/locales/fr-FR.po (1)

621-624: LGTM on FR additions and ref shifts

Copy reads well, punctuation/ellipsis look good, and keys map correctly. Ship it.

Also applies to: 1595-1598, 1637-1640, 1725-1729, 2147-2150, 2223-2225, 2452-2456, 2552-2556, 2711-2714, 2779-2782

echo/frontend/src/locales/es-ES.po (2)

2771-2782: New status string: perfecto

“Transcripción en progreso…” matches tone of existing “Transcripción en progreso.”. No change needed.

---

621-624: Anchor updates only — LGTM

References moved; copy looks good for “Conversaciones”, search/sort, “Locutor”, and transcript strings.

Also applies to: 1595-1598, 2147-2150, 2222-2225, 2239-2242, 2470-2473, 2771-2774

echo/frontend/src/locales/de-DE.po (1)

617-620: Approve — anchors shifted; translations intact. LGTM.
rg smoke-check confirms the msgids exist in de-DE and across locales; no action required.

echo/frontend/src/locales/nl-NL.po (1)

694-697: LGTM on updated anchors and strings

Translations and placeholder/tag preservation look solid: “Conversations”, “Options”, “Reset All Options”, “Search conversations”, “Sort”, “Speaker”, “Tags”, “Transcript not available”, and the long empty‑state with nested tags.

Also applies to: 1753-1756, 1895-1899, 2350-2353, 2426-2428, 2664-2668, 2682-2685, 2762-2766, 3015-3018

[coderabbitai]

🧹 Nitpick

Unify tone for “Transcription in progress…”

German string mixes styles with earlier “Transkription wird durchgeführt.”. Align for consistency.

Apply:

-msgid "Transcription in progress…"
-msgstr "Transkription läuft…"
+msgid "Transcription in progress…"
+msgstr "Transkription wird durchgeführt…"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	#: src/components/conversation/ConversationChunkAudioTranscript.tsx:67
	msgid "Transcript not available"
	msgstr "Transkript nicht verfügbar"
	#: src/components/project/ProjectTranscriptSettings.tsx:95
	#~ msgid "Transcript Settings"
	#~ msgstr "Transkript-Einstellungen"
	#: src/components/conversation/ConversationChunkAudioTranscript.tsx:69
	msgid "Transcription in progress…"
	msgstr "Transkription läuft…"
	#: src/components/conversation/ConversationChunkAudioTranscript.tsx:67
	msgid "Transcript not available"
	msgstr "Transkript nicht verfügbar"
	#: src/components/project/ProjectTranscriptSettings.tsx:95
	#~ msgid "Transcript Settings"
	#~ msgstr "Transkript-Einstellungen"
	#: src/components/conversation/ConversationChunkAudioTranscript.tsx:69
	msgid "Transcription in progress…"
	msgstr "Transkription wird durchgeführt…"

🤖 Prompt for AI Agents

In echo/frontend/src/locales/de-DE.po around lines 2771 to 2782, the German
translation for "Transcription in progress…" uses "Transkription läuft…", which
is inconsistent with the earlier style "Transkription wird durchgeführt.";
update the msgstr for the "Transcription in progress…" entry to "Transkription
wird durchgeführt." (use a period, no ellipsis) to match tone and formatting
across the file.

[coderabbitai]

🧹 Nitpick

Drop Markdown italics in UI copy.

ZpJ0wx includes asterisks: "Transkription wird durchgeführt.". Unless the renderer supports Markdown, this will leak raw asterisks. Use plain text.

🤖 Prompt for AI Agents

In echo/frontend/src/locales/de-DE.ts around line 1, the ZpJ0wx translation
contains Markdown-style asterisks ("*Transkription wird durchgeführt.*") which
will render raw asterisks in the UI; update the JSON value to plain text
("Transkription wird durchgeführt.") (edit the string inside the JSON.parse
payload), ensure the file still parses as valid JSON, and run the
build/lint/tests to confirm no regressions.

---

🧹 Nitpick

Consolidate duplicate “in-progress transcript” strings.

You now have three phrasings for the same state:

• "Transkription läuft…" (0l9syB)
• "Transkript wird verarbeitet" (NQiPr4)
• "Transkription wird durchgeführt." (ZpJ0wx)

Pick one (recommend: "Transkription läuft…") and route all usages to it to avoid inconsistent UX.

🤖 Prompt for AI Agents

In echo/frontend/src/locales/de-DE.ts (around line 1), there are three distinct
message keys for the same in-progress transcript state (0l9syB: "Transkription
läuft…", NQiPr4: "Transkript wird verarbeitet", ZpJ0wx: "*Transkription wird
durchgeführt.*"); consolidate them by choosing "Transkription läuft…" as the
canonical text, update the JSON so NQiPr4 and ZpJ0wx return the exact same
string (remove asterisks/formatting), and then search the codebase for usages of
NQiPr4 and ZpJ0wx and refactor callers to use the canonical key (0l9syB) or keep
the duplicate keys only if you must preserve IDs but ensure identical string
values everywhere.

[coderabbitai]

🧹 Nitpick

Normalize ellipsis usage in en-US

New string uses the Unicode ellipsis (…). Elsewhere we often use three dots (...). Pick one standard and stick to it. If aligning to three dots, update as below.

-msgid "Transcription in progress…"
-msgstr "Transcription in progress…"
+msgid "Transcription in progress..."
+msgstr "Transcription in progress..."

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	#: src/components/conversation/ConversationChunkAudioTranscript.tsx:69
	msgid "Transcription in progress…"
	msgstr "Transcription in progress…"
	#: src/components/conversation/ConversationChunkAudioTranscript.tsx:69
	msgid "Transcription in progress..."
	msgstr "Transcription in progress..."

🤖 Prompt for AI Agents

In echo/frontend/src/locales/en-US.po around lines 2857 to 2860, the string uses
a Unicode ellipsis (…) while the project standard is three dots (...); update
both msgid and msgstr to replace the single-character ellipsis with three ASCII
dots so the file matches the rest of the locale strings and the chosen style
guide.

[coderabbitai]

🛠️ Refactor suggestion

Prefer “Locuteur” for transcript speaker label

“Orateur” can imply public speaker; in transcription UIs “Locuteur” is standard (or “Intervenant”). Recommend “Locuteur”.

-msgid "Speaker"
-msgstr "Orateur"
+msgid "Speaker"
+msgstr "Locuteur"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	#: src/components/conversation/ConversationChunkAudioTranscript.tsx:29
	msgid "Speaker"
	msgstr "Orateur"
	#: src/components/conversation/ConversationChunkAudioTranscript.tsx:29
	msgid "Speaker"
	msgstr "Locuteur"

🤖 Prompt for AI Agents

In echo/frontend/src/locales/fr-FR.po around lines 2470 to 2473, the translation
for the transcript label uses "Orateur" but the project prefers "Locuteur" (or
"Intervenant"). Update msgstr "Orateur" to msgstr "Locuteur" for the msgid
"Speaker" so the transcript UI uses the standard French term.

[coderabbitai]

🧹 Nitpick

Terminology consistency: use “trefwoorden” instead of “tags”

Elsewhere “Tags” → “Trefwoorden”. Mirror that here.

 msgid "Search tags"
-msgstr "Zoek tags"
+msgstr "Zoek trefwoorden"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	#: src/components/conversation/ConversationAccordion.tsx:1016
	msgid "Search tags"
	msgstr "Zoek tags"
	#: src/components/conversation/ConversationAccordion.tsx:1016
	msgid "Search tags"
	msgstr "Zoek trefwoorden"

🤖 Prompt for AI Agents

In echo/frontend/src/locales/nl-NL.po around lines 2442 to 2445, the Dutch
translation uses "tags" ("Zoek tags") which is inconsistent with the project's
preferred term "trefwoorden"; update the msgstr to use "Zoek trefwoorden" (and
ensure plural/capitalization matches other translations) so it reads
consistently across the app.

[coderabbitai]

🧹 Nitpick

Prefer idiomatic, consistent phrasing for “in progress”

Across the app we use the “… wordt verwerkt” pattern. Suggest aligning this new string for consistency and more natural Dutch.

 msgid "Transcription in progress…"
-msgstr "Transcriptie wordt uitgevoerd…"
+msgstr "Transcript wordt verwerkt…"

🤖 Prompt for AI Agents

In echo/frontend/src/locales/nl-NL.po around lines 3023 to 3026, the Dutch
translation for "Transcription in progress…" uses "Transcriptie wordt
uitgevoerd…", which is inconsistent with the app's idiomatic phrase; change the
msgstr to "Transcriptie wordt verwerkt…" to match the “… wordt verwerkt” pattern
used elsewhere for consistency and natural phrasing.