ClipAn MXF clip won't play (or plays without hardware acceleration).
MXF is a container and can hold several different codecs. Inspect Playback Diagnostics and the available setup checks for the exact file, decoder, and missing component. Some files use a playback derivative rather than direct hardware playback. Preserve the original and test a representative clip; installing an additional codec package does not guarantee support for every MXF variant.
The AI section says a model isn't installed.
Open Settings → AI → Models and inspect the installed files and engine status. Follow the available setup path for a supported model, or configure a compatible endpoint. Large reasoning models are not guaranteed to be bundled with the installer. If the model is installed but fails to load, check memory headroom, the model format, server status, and the first error before retrying a batch.
A field or subject shows a dot/chip but nothing is in my exports.
Inspect whether the record is a pending proposal, a confirmed field, or subject evidence with a separate review state. Check the project scope and the enabled export format. Review and apply the intended value, then verify the actual output. A visible chip alone does not establish that a specific downstream format contains that value.
A card sits at "Checking…" forever, or the whole Ingest tab froze on one card.
Inspect the card reader, mount availability, and Jobs state. If the source disconnects or the operating system cannot read it, preserve it and reconnect using a known working reader before retrying. Do not infer a successful copy from a stalled check. Keep the visible error and diagnostics so the failing boundary can be identified.
A clip shows an orange drive badge and won't play.
That's the offline badge: the clip's file isn't reachable right now because its volume is unmounted, the file moved, or the project arrived via sync onto a machine that never had the media. Its metadata still displays from the index, and nothing is deleted; reconnect the volume (or restore the file) and it comes back live. An unmounted drive is never treated as a deletion.
A clip's provenance badge says "provenance unrecorded."
The clip was analysed before per-clip provenance existed, so whether its frames stayed local wasn't recorded, and the badge refuses to guess rather than claim "local" without a stored fact. Re-reason the clip and the new result records its provenance.
Sidecar files are cluttering a delivery folder.
Review the output switches in Sharing & Privacy. For a delivery that needs media alone, make a deliberate delivery copy while retaining the source archive and its metadata. Turning off JSON changes portability and backup requirements. Do not delete the only portable copy of a log because the receiving folder looks cleaner without it.
Rush says "insufficient credits" or "too many active jobs."
Both are exact server answers, not generic errors: the first tells you exactly how many credits you have and need (top up, or trim the batch), the second means your account's concurrent-job limit is reached; wait for a running job to finish. The pre-submit disclosure shows your balance before you confirm, so the first case normally surfaces before a submit, not after.
I renamed files in the Finder and ClipLogger "lost" my metadata.
Stop further renames and preserve the original-to-current path mapping. Reconnect the media and inspect the app's relink or recovery state. Keep associated sidecars with the correct files; a similar name or content sample is not sufficient proof for a destructive recovery. Use ClipLogger's coordinated rename workflow for future changes and validate the outcome before updating NLE references.