Option to schedule datasets in UTC or local time
When we schedule datasets today, Domo schedules them in UTC, so there are no adjustments for Daylight Savings changes.
This means that we need to reschedule datasets that must refresh at a specific time of day locally (i.e., 6 AM Central Time, regardless of whether we are in Standard or Daylight Savings time) twice a year or use another scheduling option outside of the Domo UI.
The ideal solution would be to have the option in the UI during scheduling of whether to use the local time zone or UTC when refreshing the dataset.
**Was this post helpful? Click Agree, Like, or Awesome below.**
**Did this solve your problem? Accept it as a solution!**
Comments
-
😜
1 -
@akeating , I'm with you!
1 -
Having the ability to schedule connectors to run in local time would also allow more flexibility with weekday vs. weekend scheduling.
I have a connector that I would like to run hourly Monday through Friday from 6 AM to 11 PM EST. Instead, the connector starts running Sunday at 7 PM EST and stops running Friday at 7 PM EST because the day of the week has changed in UTC.
I've confirmed with the Engineering team via Domo Support that everything is working correctly, and this is a limitation of the current scheduling options.
0 -
This burns me 2x a year
0
Categories
- All Categories
- 1.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 282 Workbench
- 3 Cloud Amplifier
- 4 Federated
- 2.8K Transform
- 86 SQL DataFlows
- 548 Datasets
- 2.2K Magic ETL
- 3.2K Visualize
- 2.3K Charting
- 544 Beast Mode
- App Studio
- 26 Variables
- 566 Automate
- 134 Apps
- 411 APIs & Domo Developer
- 21 Workflows
- DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 345 Distribute
- 87 Domo Everywhere
- 257 Scheduled Reports
- 1 Software Integrations
- 85 Manage
- 84 Governance & Security
- 8 Product Release Questions
- Community Forums
- 41 Getting Started
- 27 Community Member Introductions
- 81 Community Announcements
- 4.8K Archive