Model download fails
Symptoms
Section titled “Symptoms”A model-requirement dialog, Model Manager, or optional background preparation reports a failed download or pull.
Likely causes
Section titled “Likely causes”Network access, the model source or registry, local runtime availability, available disk space, or a changed catalog artifact can block the transfer.
Fast checks
Section titled “Fast checks”Confirm network access, identify whether the failed transfer is Whisper, Ollama, or the embedding model, then use Refresh in Model Manager after the operation ends.
Resolution
Section titled “Resolution”Retry the same required model from the model-requirement dialog or Model Manager. Keep Local Mode selected for local Ollama pulls. If it repeatedly fails, postpone the dependent workflow instead of changing unrelated session data.
Data-loss warning
Section titled “Data-loss warning”Deleting a model removes that model; it does not repair a transfer failure or preserve an incomplete download. Do not reset sessions to resolve a model download.
Information to collect for support
Section titled “Information to collect for support”Collect the model identifier, transfer type, exact error, network environment, application version, provider mode, and whether the failure happens from a clean application data directory.