Skip to main content
waffle.svg
Domo Knowledge Base

Common Workbench Errors

Intro

This is a troubleshooting guide for the most common errors that users encounter when using Workbench to import data into Domo.

"Job Cannot Change Schema Dynamically"

Cause

  • Occurs when a file that was previously uploaded has new columns added to it, one or more of the columns have been renamed, or the columns have been reordered in the original source. Jobs will also fail when the data type of a column is changed (e.g. from "Date" to "Text").

  • There is a setting called Allow schema changes available for jobs in Workbench. It is disabled by default, but when enabled, it allows dynamic schema changes to occur. To locate this option, click wb5_jobs_icon.png and choose a job in the list, click the Configure subtab, then scroll down to Additional settings at the bottom.

Notes and Recommendations

  • Adding new columns and reordering columns is generally safe, but Domo does not recommend deleting columns.

  • To ensure that cards and DataFlows based on the DataSet do not break, leave the schema the same.

Solution(s)

  • Revert the changes. If possible, revert any changes that were made to the original data source that caused the schema to change.

  • Manually running the job once via the Workbench UI updates the schema, regardless of the setting for Allow schema changes in Configure > Additional settings in Workbench.

  • If you are confident that your changes will not affect existing cards or DataFlows, you can change the option in Additional settings to allow the schema to be set dynamically. If you decide to enable it, Domo recommends disabling it once you fix the DataSet.

"Source File Doesn't Exist"/"File Not Found"

Cause

The file does not exist in the location specified in the Source menu in the Configure subtab for the selected job in Workbench.

Solution

  • Update the file path in the Source menu in the Configure subtab for the selected job in Workbench with the correct file name and location.

  • Make sure the file is in the right location and has the name specified in Workbench.

  • If the file is not local to the machine, consider setting up impersonation with a user that has access to the file. 

"504 Gateway Timeout"

Cause

This error occurs when there is a communication error between Workbench and your Domo instance.

Solution

  • If this is the first time you are attempting to use Workbench, you will need to make sure that the proxy settings in Workbench are configured properly. Proxy settings can be configured in Workbench in Settings > Proxy. To locate Settings, click wb5_more_icon.png in the left-hand icon bar. 

  • Make sure your network is configured to allow access to Domo.

  • If your Domo Workbench jobs have worked previously, you may be able to resolve this by re-running the job.

"File Is In Use"

Cause

The file that Workbench is trying to import to Domo is in use by another application and/or the file is locked. This can happen if the file is in use, such as when the file is being copied when the Workbench job runs.

Solution

  • Ensure that the file is not in use when the Workbench job runs.

  • Change the schedule of the job so that the file won’t be in use when Workbench runs.

"Deadlock Victim"

Cause

This is a SQL error that occurs when you are attempting to import data from a database. It often happens when different queries attempt to access a record at the same time. The database software decides which query is allowed to run and will block other queries.

Solution

  • Update the Workbench schedule for the job to run when other queries are not running against the database.

  • Review other queries that may be running at the same time and change when the queries run.

  • Consider using a non-locking query. Keep in mind that a change like this can give you dirty data if the data is actively being updated.

"Connection Login Timeout" when using ODBC plugin

Cause

This often occurs when the database is under a heavy load.

Solution

Retry the Workbench job at a different time when the load on the database is lower.