Troubleshooting Omni Connector Jobs¶

Driver Logging¶

Omni connector jobs support two logging parameters in the job’s input section. These are the primary diagnostic tools for connection and data problems, and Zuar support will often ask for a driver log file when investigating an issue.

Parameter	Type	Description
`log_level`	integer	Driver log verbosity, from 1 (least) to 5 (most).
`collect_raw_log`	boolean	Write the driver log to a standalone file.

To capture a log file for a support case:

Edit the job’s configuration and add the parameters to the input section:

"input": {
    "use": "omni_salesforce.iov2.input#OmniConnectorInput",
    "table": "Account",
    "credentials": "my_salesforce_credentials",
    "log_level": 3,
    "collect_raw_log": true
}

Save and run the job once, reproducing the problem.
The log file is written on the Runner instance to /var/mitto/cdata/<job name>_<timestamp>.log. The exact path is also written to the job’s log output. Attach this file to your support ticket; Zuar support can help retrieve it if you do not have access to the instance’s filesystem.
Remove the parameters (or set collect_raw_log to false) when done. High verbosity levels produce large files and can slow the job down, so use them only while diagnosing.

Use a higher log_level only if support asks for it; level 3 is a common starting point.

Common Errors¶

Licensing errors¶

If a job fails with a licensing error, or the wizard reports a license problem when testing credentials, contact Zuar support . This includes jobs whose connector was removed on the Licensing page; reinstall the connector or delete the jobs.

Rejected credentials¶

“The service rejected the supplied credentials” from the wizard means the connected service refused the sign-in. Re-check the values (and the authentication scheme) and try again. For OAuth, re-run the AUTHENTICATE step to obtain fresh tokens.

Wizard cannot list tables¶

The Select Tables step connects to the service to list its tables. If it fails, the underlying driver error is shown. Typical causes are missing permissions for the connected account or service-side settings; the connector’s reference documentation (linked from the Connectors page) describes what the service must allow.

Wizard icon missing or disabled¶

If a connector’s wizard icon is missing from the + Add Job page, the connector is not installed; see Installing Omni Connectors. If the icon appears in the Disabled group, the connector is installed but not licensed; clicking it opens Settings.