Why do I keep getting an 'out of date' error display on my data sets?
I have most of my workbench data sets scheduled to run periodically. I seem to see an 'out of date' error on many of them, and I'm not sure why. I run them manually and the error goes away, and then the next time the update is scheduled to run, the error reappears (even though according to the workbench 'last execution' as well as the 'last updated' on the data set it ran successfully at or near the scheduled time).
I'm not sure what the error message is trying to tell me - these are all 'replace' data sets so we're not missing any data that we'd need to deal with. Anyone else receive this error?
Comments
-
I think I've seen this before. I think it's pretty harmless. There may be some kind of miscommunication between when the datasource was uploaded from Workbench and it's "last updated date". It might be worth reaching out to Domo Support about and having the product team look into your specific case and see if there's anything that needs to be tweaked or fixed.
0 -
@ej_jodi_k, did quinnj's reply answer your question?
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 101 SQL DataFlows
- 622 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 748 Beast Mode
- 59 App Studio
- 41 Variables
- 686 Automate
- 176 Apps
- 453 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 396 Distribute
- 113 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 125 Manage
- 122 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 109 Community Announcements
- 4.8K Archive