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.5K Connect
- 1.2K Connectors
- 296 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 614 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 729 Beast Mode
- 53 App Studio
- 40 Variables
- 677 Automate
- 173 Apps
- 451 APIs & Domo Developer
- 45 Workflows
- 8 DomoAI
- 34 Predict
- 14 Jupyter Workspaces
- 20 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 121 Manage
- 118 Governance & Security
- Domo Community Gallery
- 32 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive