Product support from the developer.

Copy installation details from Omni

In your site's Umbraco backoffice, open Translation → Support. Choose Copy support details, review the text and paste it into the optional technical details area of the contact form.

The summary shows detected versions and AI components, configured languages, chat provider/model choices and selected translation settings. Profile names and aliases are omitted unless you choose to include them. It does not include credentials, licence keys, connection strings, content or prompts. Review the text before sharing.

If your installed version does not have this dashboard, enter your Umbraco and Omni versions manually and describe your provider and the relevant error. The public website cannot open your private backoffice directly.

Enable diagnostic logging

For a repeatable issue, merge these settings into your site'sappsettings.Development.json (or the settings file for the environment you are investigating), preserving existing configuration. Restart the site, then reproduce the problem once and note the time and translation job ID.

{
  "DiploTranslatorOmni": {
    "Diagnostics": {
      "Enabled": true,
      "DevelopmentOnly": true,
      "IncludeRawValues": false
    }
  },
  "Serilog": {
    "MinimumLevel": {
      "Override": {
        "Diplo.Translator.Omni": "Debug",
        "Umbraco.AI": "Debug"
      }
    }
  }
}

The Debug overrides capture detailed Omni and Umbraco.AI activity, including Omni's request timing, retries and timeout messages. For the most detailed trace logging, temporarily use Verboseinstead of Debug; Serilog calls its trace levelVerbose. If your host restricts the log output to higher levels, its logging configuration must also allow these events.

Omni's Diagnostics settings additionally write a JSON file for each content translation job toApp_Data/DiploTranslatorOmni/Diagnostics/<job-id>.json, relative to the site root. These files record property and text-unit outcomes, translation attempts, validation and save checks. They are separate from Umbraco's application logs.

With DevelopmentOnly: true, JSON capture runs only in the Development environment. To diagnose another environment, apply the settings there and temporarily set DevelopmentOnly tofalse. Keep IncludeRawValues set tofalse so source and translated values remain redacted. Turn off diagnostic capture and restore your normal log levels after investigating.

Check the Umbraco logs

1. Open Settings → Log Viewer in the Umbraco backoffice. Ask an administrator if you do not have access.
2. Select the time range covering the failed preview or job. Start with Warning and Error entries, then include Debug or Verbose entries if you enabled them before reproducing the issue.
3. Search for Diplo.Translator.Omni, Umbraco.AIor the installed provider's name. Inspect the message, exception andSourceContext to identify the component involved. Use a job ID or content key where the log entry includes one.
4. Look for provider authentication or rate-limit errors, timeouts, validation failures and save errors. Compare their timestamps with the Translation Jobs report and the matching Omni diagnostic file.

In the Log Viewer's query search, filter by component with:

StartsWith(SourceContext, 'Diplo.Translator.Omni') or StartsWith(SourceContext, 'Umbraco.AI')

With Umbraco's default file logging, logs are stored inumbraco/Logs under the site root. Hosting configuration may route them elsewhere; check your hosting platform's log tools if they are not available in the backoffice.

Share only the relevant, sanitised excerpt. Diagnostic files can still contain requester details, identifiers and error messages even with raw values disabled, so review them before sharing. See the diagnostics configuration reference and Umbraco's Serilog documentation for configuration details.