Workbench 4.5 Error: Object reference not set to an instance of an object

I am running Workbench 4.5 and when I migrated my Workbench 2.0 jobs I noticed that some were left out. When try to import them into Workbench 4.5 one by one I get this error: "Object reference not set to an instance of an object."
Has anyone else experienced this error and does anyone know what's causing it?
Comments
-
Hi all,
Can anybody help out @IntelliVince?
Thanks!0 -
Hi there,
I see that this thread was put in nearly a month ago. If it is still an issue, I'd like you to contact Domo Support at 801-805-9505, [email protected] via email, or Buzz them from your instance. Typically an error like this occurs from a null exception that is pointing to a null value. There could be multiple outlets to look at in order to fix this error.
They'd be glad to help, and they're expecting your case.
Thanks
1 -
FYI -- I am getting the same error message and was searching for a solution. I will go ahead and contact support.
0
Categories
- 10.6K All Categories
- 8 Connect
- 918 Connectors
- 250 Workbench
- 474 Transform
- 1.7K Magic ETL
- 69 SQL DataFlows
- 478 Datasets
- 214 Visualize
- 259 Beast Mode
- 2.1K Charting
- 12 Variables
- 19 Automate
- 356 APIs & Domo Developer
- 89 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 249 Distribute
- 65 Domo Everywhere
- 243 Scheduled Reports
- 21 Manage
- 42 Governance & Security
- 191 Product Ideas
- 1.2K Ideas Exchange
- 11 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive