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.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 302 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 104 SQL DataFlows
- 633 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 760 Beast Mode
- 62 App Studio
- 42 Variables
- 699 Automate
- 181 Apps
- 457 APIs & Domo Developer
- 51 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 401 Distribute
- 116 Domo Everywhere
- 277 Scheduled Reports
- 8 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 111 Community Announcements
- 4.8K Archive