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.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 753 Beast Mode
- 61 App Studio
- 41 Variables
- 692 Automate
- 177 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive