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.
3
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 308 Workbench
- 7 Cloud Amplifier
- 10 Federated
- 3.8K Transform
- 660 Datasets
- 117 SQL DataFlows
- 2.2K Magic ETL
- 818 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 84 App Studio
- 46 Variables
- 781 Automate
- 191 Apps
- 483 APIs & Domo Developer
- 84 Workflows
- 23 Code Engine
- 43 AI and Machine Learning
- 22 AI Chat
- 3 AI Projects and Models
- 18 Jupyter Workspaces
- 409 Distribute
- 116 Domo Everywhere
- 282 Scheduled Reports
- 11 Software Integrations
- 146 Manage
- 142 Governance & Security
- 8 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 115 Community Announcements
- 4.8K Archive