bryandelacruz | 2022-03-10 06:09:52 UTC | #1
How in the heck do I update a sequence schedule to 6pm or later? There isn't a single thing on the web that explains that platform API falls on its face if you go beyond 24:00. Below is the JSON for 4:30pm - 5:30pm after military time is subtracted by UTC time. Talk about frustrating.
{ "name": "AAVMCollectionsC2P", "version":11, "intervals": [ { "start": "2022-3-08T22:30:00.784Z", "end": "2022-3-08T23:30:00.784Z" } ], "timeZone": "America/NewYork", "sequence": { "id": "7ee41210-947d-43bf-9a95-0ed1097d9619", "name": "AAVMCollectionsC_2P", "selfUri": "/api/v2/outbound/sequences/7ee41210-947d-43bf-9a95-0ed1097d9619" } }
tim.smith | 2022-03-10 16:46:15 UTC | #2
Hello, please refer to https://en.wikipedia.org/wiki/ISO_8601#Times for information on ISO-8601 timestamps. Specifically this part about times:
ISO 8601 uses the 24-hour clock system. As of ISO 8601-1:2019, the basic format is T[hh][mm][ss] and the extended format is T[hh]:[mm]:[ss]. Earlier versions omitted the T (representing time) in both formats.
In your calculation, 5:30 PM translates to 23:30:00 UTC. To add 30 minutes to that, you would end up with 24:00:00, which isn't valid because that time doesn't exist; that's 00:00:00 the next day. E.g. 2022-3-08T23:30:00.784Z + 30 minutes is 2022-3-09T00:00:00.784Z.
bryandelacruz | 2022-03-10 16:47:11 UTC | #3
Thank you so much! I couldn't figure that out myself for the life of me.
system | 2022-04-10 16:47:46 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 13865