WORKBENCH scheduling enhancement - Australia, Sydney Trains
Options
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.5K Product Ideas
- 1.5K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 278 Workbench
- 4 Cloud Amplifier
- 4 Federated
- 2.7K Transform
- 89 SQL DataFlows
- 562 Datasets
- 2K Magic ETL
- 3.4K Visualize
- 2.3K Charting
- 583 Beast Mode
- 13 App Studio
- 28 Variables
- 585 Automate
- 142 Apps
- 415 APIs & Domo Developer
- 27 Workflows
- 1 DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 359 Distribute
- 98 Domo Everywhere
- 259 Scheduled Reports
- 2 Software Integrations
- 94 Manage
- 91 Governance & Security
- 9 Product Release Questions
- Community Forums
- 37 Getting Started
- 28 Community Member Introductions
- 89 Community Announcements
- 4.8K Archive