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
- 311 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3.8K Transform
- 657 Datasets
- 115 SQL DataFlows
- 2.2K Magic ETL
- 815 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 81 App Studio
- 45 Variables
- 775 Automate
- 190 Apps
- 481 APIs & Domo Developer
- 81 Workflows
- 23 Code Engine
- 40 AI and Machine Learning
- 20 AI Chat
- 1 AI Playground
- 1 AI Projects and Models
- 18 Jupyter Workspaces
- 410 Distribute
- 120 Domo Everywhere
- 280 Scheduled Reports
- 10 Software Integrations
- 144 Manage
- 140 Governance & Security
- 8 Domo Community Gallery
- 48 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 114 Community Announcements
- 4.8K Archive