When you make a scheduled deployment, the correct date/time specified from OttoDeploy does not reflect in the created schedule in the destination server’s Admin Console.
Schedule date/time in OttoDeploy:
Schedule date/time in Admin Console (destination server):
Hey Jim,
OttoFMS does no manipulation of the date/time you put in before it passes it to FileMaker to make that schedule. In fact the reason it requires you to enter it in server time is that FileMaker only accepts times that are in the server timezone and not a UTC time or something similar.
Where is this server located? Is it possible its trying to account for daylight saving somehow?
-Kyle
I created the deployment schedule using the OttoDeploy app, which is hosted in Singapore, while the destination server is located in Mexico. I expected the scheduled time to match what I entered in OttoDeploy.
Although the app notes that the schedule uses the destination server’s date and time, the actual deployment showed up an hour ahead when viewed in the Mexico admin console.
Hey JIm,
Which version of FIleMaker are you on? Looks like others have reported a similar issue when making schedules on a server in Mexico:
https://community.claris.com/en/s/question/0D5Vy000006BLkNKAW/filemaker-server-is-using-daylight-savings-time-for-mexico
OttoFMS is using the FileMaker API to make the schedules that run deployments, if there is a bug in filemaker that incorrectly handles the times there is very little OttoFMS can do to handle it.
If you make a schedule via the FIleMaker Admin API or the FileMaker Admin Console do the times match up?
-Kyle
I tried creating a test schedule in the Mexico admin console and that too has the incorrect time. Thank you for pointing this out. I didn’t realize this was happening until now.
