Trace Audio Notes & Insights

Last updated: September 5, 2026

Trace Support.

If transcription or analysis fails, first check your Gemini API key, project quota, audio format, and foreground processing state.

What is happening?

Before contacting support

Please confirm:

  • Trace has microphone permission. If you previously denied access, enable it in iOS Settings.
  • You entered a valid Gemini API key in Settings.
  • The Google project that owns the key still has available quota.
  • The app stays in the foreground for longer audio processing. If iOS interrupts background execution, return to the app and retry the unfinished workflow.
  • The imported file is in an audio format supported by the app.
  • If a call, another app, or an audio device interrupts recording, return to Trace and confirm the recording state before continuing or finishing.
  • If sharing audio or a result fails, reopen that item and use the system Share Sheet again.

If the issue keeps happening, you can leave public feedback through an App Store review.

Apple Watch recording

Trace can record locally on Apple Watch. When you finish, the recording transfers to its paired iPhone and appears in the Recording Inbox the next time Trace is active; the watch keeps its copy until the iPhone confirms durable receipt. If it has not appeared, confirm that both devices remain paired, unlocked, and connected, then open Trace on iPhone.

Gemini API errors

Trace sends Gemini requests directly from your device to Google Gemini API using your own key. Use the app’s current job status to confirm what is saved, waiting or unfinished.

Find your symptom below. Keep the source audio and existing result while investigating; an error alone does not prove data loss or successful saving.

Recording could not finish

What happened: A finalization failure does not by itself prove that the audio was lost or fully saved.

Current state: The audio may still need finalization. Confirm it appears in Recordings and plays fully; the error alone cannot guarantee that it was saved.

What to do: Check Recordings first. In 1.3.1 and later, tap a recording marked Waiting for recovery to retry. In 1.3.0 or earlier, close and reopen Trace, then check again. Do not delete the app or source audio.

Transcript stops partway through

What happened: Google can return text that omits the end. Text or a completed response alone does not prove full coverage.

Current state: Returned text may cover only part of the audio, including omissions at the beginning, middle or end. Timestamp checks cannot guarantee that every sentence was recognized.

What to do: When Trace detects a missing tail and recovery is eligible, it attempts recovery. Only a retry shown in the job status confirms that more processing is scheduled. If a completed result clearly ends early, keep the audio and result and report the issue through an App Store review. Do not delete the original result or repeatedly submit the entire recording.

Network interruption or timeout

What happened: The connection or processing did not finish within its deadline. The error alone does not establish whether Google completed the work.

Current state: The job may be failed, waiting to retry or still processing. Check the original job; a timeout does not prove Google stopped processing.

What to do: Check your connection and return to the app to resume unfinished work as its status allows. Wait if the app shows a pending retry. Do not create duplicate jobs or trim away audio as a first response.

Quota or rate limit

What happened: HTTP 429 can mean a short-term rate limit or a daily or project quota limit. Another key from the same project may share that limit.

Current state: This request was limited, and the whole job may be unfinished. Check the app for completed work and any scheduled retry time.

What to do: A retry is scheduled only when the app shows a countdown. If failures persist, check project limits and billing in Google AI Studio. Avoid repeatedly tapping Retry.

Key, permissions or billing

What happened: A 401 usually concerns authentication. A 403 can also involve project permissions or access requirements; it does not always mean the key was entered incorrectly.

Current state: This request did not receive normal authorization or access. This error does not mean local source audio or existing results were deleted.

What to do: Check the key in Trace Settings and the key, project access and billing status in Google AI Studio, as the error indicates. Never include API keys in support messages, screenshots or websites.

Model or file resource not found

What happened: HTTP 404 may refer to an unavailable model or to a file or job resource that no longer exists on Google.

Current state: The requested Google resource is unavailable; that does not mean the local audio is gone. Check whether the original job still has its source.

What to do: Follow the app’s message. Refresh the model list in Settings for a model issue; resume the existing job for unfinished work. Changing modes is a separate choice that may affect results and cost, not a universal repair.

Google service temporarily unavailable

What happened: HTTP 500 or 503 generally indicates a server-side processing failure or temporary unavailability. It does not prove that the app or input is fault-free.

Current state: This attempt did not finish normally. Check the original job to see whether completed work is available or a retry is scheduled.

What to do: Check Google service status and retry the existing job later. For repeated failures, report the error code and time through an App Store review. Changing models or deleting audio is not the first step.

Request content or parameters rejected

What happened: HTTP 400 means Google could not accept the request. A more specific message may identify a key, billing or feature restriction.

Current state: The request was rejected and cannot count as a completed transcription. Keep the source audio and existing result.

What to do: Follow the specific message first. If the cause is unclear, check that the app is up to date and report the issue through an App Store review. Do not delete recording content just to experiment.

Unknown error? Keep the code and approximate time, check the job status, and leave an App Store review without sharing keys or private audio.

Error Common meaning What to try
HTTP 400 / INVALID_ARGUMENT The request format, context, or model parameters were not accepted by Gemini. See the explanation and next step above
HTTP 401 / HTTP 403 / PERMISSION_DENIED The API key, Google project permission, or billing state does not allow this request. See the explanation and next step above
HTTP 404 / NOT_FOUND The selected model or an uploaded Gemini file resource could not be found. See the explanation and next step above
HTTP 429 / RESOURCE_EXHAUSTED Your Gemini quota or rate limit was reached. See the explanation and next step above
HTTP 500 / INTERNAL Google processing failed; the specific cause depends on the error details. See the explanation and next step above
HTTP 503 / UNAVAILABLE The Gemini service may be temporarily overloaded or unavailable. See the explanation and next step above
HTTP 504 / DEADLINE_EXCEEDED Gemini did not finish within the deadline; audio length is not necessarily the cause. See the explanation and next step above

Official sources: Gemini API troubleshooting guide and Gemini audio understanding.

Privacy summary

Trace uses your own Gemini API key, which is stored only on this device. Audio and related content are sent to Google for processing. Longer recordings are processed in sections, and the audio is held temporarily on Google's servers while that happens; Trace makes a best-effort attempt to delete it afterwards. See the Privacy Policy for data types, retention periods, and your choices.