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, support@domo.com 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
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 311 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3.8K Transform
- 658 Datasets
- 116 SQL DataFlows
- 2.2K Magic ETL
- 815 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 82 App Studio
- 45 Variables
- 775 Automate
- 190 Apps
- 481 APIs & Domo Developer
- 81 Workflows
- 23 Code Engine
- 40 AI and Machine Learning
- 20 AI Chat
- 1 AI Playground
- 1 AI Projects and Models
- 18 Jupyter Workspaces
- 410 Distribute
- 120 Domo Everywhere
- 280 Scheduled Reports
- 10 Software Integrations
- 144 Manage
- 140 Governance & Security
- 8 Domo Community Gallery
- 48 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 114 Community Announcements
- 4.8K Archive