Dataset jobs not running on set schedule
Comments
-
Including screenshots of a job that did run, vs a job that didn't run.
0 -
Also seeing some jobs that haven't run for multiple days. See attached screenshot.
0 -
Old topic, but I'm curious if you found a solution to this. I have run into the exact same problem, where the "next scheduled" day is a day that has passed. I have found that this can be computer dependent, as I had no issues on one machine, but it has happened on the other.
Running Workbench 4.62.
0 -
I don't believe we've ever found a resolution to this. We've ran into it again recently and just rebooted the dedicated VM that runs Workbench.
0 -
We are also seeing the same issue on a dedicated server.
Sometimes it just does not run for days.
We have gone through the configs and everything seems to be setup correctly.
And to be clear: the job does run as expected ~70% of time.
0
Categories
- 10.5K All Categories
- 8 Connect
- 918 Connectors
- 250 Workbench
- 470 Transform
- 1.7K Magic ETL
- 69 SQL DataFlows
- 477 Datasets
- 193 Visualize
- 252 Beast Mode
- 2.1K Charting
- 11 Variables
- 17 Automate
- 354 APIs & Domo Developer
- 89 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 247 Distribute
- 63 Domo Everywhere
- 243 Scheduled Reports
- 21 Manage
- 42 Governance & Security
- 174 Product Ideas
- 1.2K Ideas Exchange
- 12 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive