Documentation

Troubleshooting

Resolve common provider, permissions, content and background-job problems.

No chat provider is available

Confirm that an Umbraco.AI chat provider is installed and works in the host site. Check that a configured ChatProfileAlias exists, or that the administrator-managed profile is still live and whitelisted.

A property is skipped

Review the preview message. The value may be empty, invariant, unsupported, already populated in the target culture or contain no safe translatable text. For a custom editor, verify its persisted value matches its mapping or adapter contract.

Recent edits are missing

Save the document first. Omni deliberately reads server-side saved content, including saved drafts, rather than unsaved browser state.

A translation job has errors

Open Translation Jobs for the per-property or per-page report. Provider timeouts and individual value errors are recorded without forcing uncertain partial values into content.

A user cannot translate content

Confirm the user is an administrator or has access to Umbraco's Translation section. Also check their browse permission for previews and update permission for the page and target culture.

A section job is rejected

The scan or selection may exceed MaxSectionPages, MaxSelectedPages or MaxSelectedPropertiesPerPage. Choose a narrower root or raise the relevant limit deliberately.

SQLite development warning

For SQLite development sites, disable Umbraco.AI analytics and audit logging and limit Omni to one concurrent request:

"Umbraco": {
  "AI": {
    "Analytics": { "Enabled": false },
    "AuditLog": { "Enabled": false }
  }
},
"DiploTranslatorOmni": {
  "MaxConcurrentTranslationRequests": 1
}

Diplo Translator Omni

Ready to translate your first draft?

Bring AI translation into the Umbraco backoffice — and keep the final say with your editors.