WORKBENCH scheduling enhancement - Australia, Sydney Trains

user01512
Member
Issue: Domo dataset was scheduled to run on 1st of every month at 08:00 AM AEST, but it ended up triggering on the 2nd of the month at 08:00 AM AEST. This is due to the back-end schedule configuration being in UTC, where 08:00 AM AEST corresponds to 10:00 PM UTC of the previous day. As there is no option to run on the last day of every month there is no way to currently schedule this job. Suggest that a change be made to allow scheduling in our local time zone that gets converted to the matching UTC time.
2
Categories
- All Categories
- 1.1K Product Ideas
- 1.1K Ideas Exchange
- 1.2K Connect
- 969 Connectors
- 257 Workbench
- Cloud Amplifier
- 1 Federated
- 2.4K Transform
- 76 SQL DataFlows
- 501 Datasets
- 1.8K Magic ETL
- 2.7K Visualize
- 2.2K Charting
- 375 Beast Mode
- 20 Variables
- 485 Automate
- 103 Apps
- 378 APIs & Domo Developer
- 6 Workflows
- 22 Predict
- 6 Jupyter Workspaces
- 16 R & Python Tiles
- 316 Distribute
- 64 Domo Everywhere
- 252 Scheduled Reports
- 59 Manage
- 59 Governance & Security
- 1 Product Release Questions
- 5K Community Forums
- 37 Getting Started
- 23 Community Member Introductions
- 63 Community Announcements
- 4.8K Archive