Daylight Savings messing with Scheduling

user16872

How are people handling the effects daylight savings has on scheduling in domo? All of my connectors and everything in workbench is now running an hour later because domo schedules everything based on UTC. From what I've read, the only way to fix this is by going through each individual dataset and scheduling it an hour earlier. There has to be a simpler way. Doing this twice a year is an inefficient use of time and it gets more and more frustrating as the number of connections we use grows.

jaeW_at_Onyx

i'm going to ask a dumb question. is there a reason why dataflows can't run at 8AM UTC year round?

you can use the javacli to execute datasets and dataflows via command line. this way you'd have control over exactly when they triggered.

https://knowledge.domo.com/Administer/Other_Administrative_Tools/Command_Line_Interface_(CLI)_Tool

jaeW_at_Onyx

i'm going to ask a dumb question. is there a reason why dataflows can't run at 8AM UTC year round?

you can use the javacli to execute datasets and dataflows via command line. this way you'd have control over exactly when they triggered.

https://knowledge.domo.com/Administer/Other_Administrative_Tools/Command_Line_Interface_(CLI)_Tool

user16872

@jaeW_at_Onyx This is in reference to collecting the data, not the dataflows. We have to change the scheduled time because for many of the software programs we get data from, there is a tight window between when the data becomes available to when the data needs to be processed and ready for company staff. We pull the data too early and we don't get the new rows. We pull it too late and it's not ready by the time our staff needs it.

jaeW_at_Onyx

@user16872

Data pipeline orchestration with PyDomo or JavaCLI are your best bets.

http://www.onyxreporting.com/blog/domo-python-tutorial-execute-datasets-and-dataflows-via-api-and-pydomo