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
- All Categories
- 1.2K Product Ideas
- 1.2K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 273 Workbench
- 2 Cloud Amplifier
- 3 Federated
- 2.7K Transform
- 78 SQL DataFlows
- 526 Datasets
- 2.1K Magic ETL
- 3K Visualize
- 2.2K Charting
- 441 Beast Mode
- 23 Variables
- 514 Automate
- 115 Apps
- 391 APIs & Domo Developer
- 8 Workflows
- 26 Predict
- 10 Jupyter Workspaces
- 16 R & Python Tiles
- 332 Distribute
- 77 Domo Everywhere
- 255 Scheduled Reports
- 67 Manage
- 67 Governance & Security
- 1 Product Release Questions
- Community Forums
- 41 Getting Started
- 27 Community Member Introductions
- 68 Community Announcements
- 4.8K Archive