# Manage order date and time **URL:** \ **Category:** GraphQL API\ **Created:** [August 30, 2022, 8:25pm UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145 "2022-08-30T20:25:23Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![marioreinike](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@marioreinike](https://community.shiphero.com/u/marioreinike)\ **Post date:** [August 30, 2022, 8:25pm UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/1 "2022-08-30T20:25:23Z")
Hi, I think somethiing’s wrong with Dates and Times when creating orders via the API. When an order is created, I also need to set the time when it needs to be fulfilled. So, I’m using the field `hold_until_date` that does that. We are using timezone “America/Santiago” (UTC -4). And this works fine when we push an order with a specific date. For example, we push an order with date “2022-08-30T20:00:00.000Z” and in Shiphero the time is shown correctly: “08/30/2022 04:00 PM”. The problem is that the order’s “Hold Until Date” and “Hold Until Time” are not working correctly, the times that are being set are not aware of the timezone, so, with the same example, if I put hold\_until\_date with the value of “2022-08-30T20:00:00.000Z”, in Shiphero App it shows “08/30/2022 08:00 PM”, that is not what I expected. It has to be “08/30/2022 04:00 PM”. Maybe am I missing some settings? ---
**Author:** ![marioreinike](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@marioreinike](https://community.shiphero.com/u/marioreinike)\ **Post date:** [August 30, 2022, 9:27pm UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/2 "2022-08-30T21:27:09Z")
Update: I tried sending the orders with local time, i.e. “2022-08-30T16:00:00.000-04:00”. And, again, the order date is set correctly, but the order hold\_until\_date is showing “2022-08-31T00:00:00+00:00” and I don’t even know why. See screenshot: mutation order\_create: ![image](https://us1.discourse-cdn.com/flex020/uploads/shiphero/original/1X/2e830ac160ae9be4d61f877699fe6d1150fe28a8.png) PS: If I send the order with hold\_until\_date in local time but without the timezone, (i.e. “2022-08-30T16:00:00”) it seems to work, but of course this is not an expected behaviour as it is not following the ISO 8601 time format. ![image](https://us1.discourse-cdn.com/flex020/uploads/shiphero/original/1X/f735d21db71b5114e40706801e6dc41035efd442.png) ---
**Author:** ![sh-agent](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@sh-agent](https://community.shiphero.com/u/sh-agent)\ **Post date:** [August 31, 2022, 11:10am UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/4 "2022-08-31T11:10:10Z")
Hey @marioreinike, Thanks for reaching out! Going to start looking into this; I’ll have an update for you shortly. Best, RayanP ---
**Author:** ![sh-agent](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@sh-agent](https://community.shiphero.com/u/sh-agent)\ **Post date:** [August 31, 2022, 9:12pm UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/5 "2022-08-31T21:12:59Z")
Hey @marioreinike, I do believe that this issue will have to be escalated to our Engineering Team to be fixed. I’ll keep you updated here as the updates come in. Thank you for bringing this to our attention. Please let me know if you have any questions or concerns! Best, RayanP ---
**Author:** ![marioreinike](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@marioreinike](https://community.shiphero.com/u/marioreinike)\ **Post date:** [August 31, 2022, 9:17pm UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/6 "2022-08-31T21:17:51Z")
Ok, thanks! 👍 👍 👍 ---
**Author:** ![Florin](https://avatars.discourse-cdn.com/v4/letter/f/91b2a8/32.png) [@Florin](https://community.shiphero.com/u/Florin)\ **Post date:** [October 18, 2022, 12:06pm UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/8 "2022-10-18T12:06:56Z")
Any updates on this? Im also having a hard time understanding how hold\_until\_date is supposed to work. For example, I set the hold\_until\_date with an automation. When I get the order via api I can see that hold\_until\_date. If I resubmit that hold\_until\_date that I just received from ShipHero with an order\_update mutation, now 5h get added to the hold\_until\_date . I am not trying to resubmit the same date, I am just using this example to outline the issue. ---
**Author:** ![sh-agent](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@sh-agent](https://community.shiphero.com/u/sh-agent)\ **Post date:** [October 18, 2022, 1:10pm UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/9 "2022-10-18T13:10:30Z")
Hey @Florin, Thanks for reaching out and welcome to our Developer Community! This issue is still making its way to our Engineering Team, I’ll go ahead and bump it. The bug here is that when you change the `hold_until_date` through the Public API it’s being displayed in UTC time in the UI when it should be in your accounts timezone. Please let me know if you have any questions or concerns. Best, RayanP ---
**Author:** ![Florin](https://avatars.discourse-cdn.com/v4/letter/f/91b2a8/32.png) [@Florin](https://community.shiphero.com/u/Florin)\ **Post date:** [October 18, 2022, 6:47pm UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/10 "2022-10-18T18:47:10Z")
Hmm, I wonder if that is the only problem. If we submit the same date we receive from the api, shouldnt the date remain the same? ---
**Author:** ![marioreinike](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@marioreinike](https://community.shiphero.com/u/marioreinike)\ **Post date:** [October 19, 2022, 10:43am UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/11 "2022-10-19T10:43:01Z")
Hi @Florin ! Good question! You made me wonder if it would happen so I gave it a try. And yes, this is an issue, because if you submit `hold_until_date` in a `order_update` mutation with the same value that you received from a `order` or `orders` query, you will find that the value is changed. In my case, my account is configured with timezone GMT -03:00. So, I got an order with `"hold_until_date": "2022-10-19T12:00:00.127000+00:00"`, then, passed the same value to an `order_update` mutation, and got that the value has been updated for +3 hours. I believe that the API is not considering UTC time values for this specific fields, so it assumes that every value is set to the local timezone configuration. It is something to consider if you’re updating orders with the same values as you get from the API. See screenshots: 1. get order query: 2. update order mutation with the same value (it got changed by 3 hours): ---
**Author:** ![marioreinike](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@marioreinike](https://community.shiphero.com/u/marioreinike)\ **Post date:** [October 19, 2022, 10:56am UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/12 "2022-10-19T10:56:53Z")
@sh-agent The problem isn’t that the hold\_until\_date is displayed as UTC in the UI. It really changes the actual Hold Until Date value to a wrong one, so, for example, if your account configuration is GMT -03:00, then all of your orders will be on hold 3 more hours as you expected. But then the problem gets bigger if you want to update an order. If you update an order by fetching all the data from the API, then update one or more values, keeping `hold_until_date` untouched, it gets changed anyway. So, every time you do an update, this value gets updated from +X hours, and enters in this endless loop of delaying the Hold Until Date value. To be clear, this just happens with the `hold_until_date` field. All of the other date fields work as expected, using local and UTC timezones. ---
**Author:** ![sh-agent](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@sh-agent](https://community.shiphero.com/u/sh-agent)\ **Post date:** [October 19, 2022, 11:22am UTC](https://community.shiphero.com/t/manage-order-date-and-time/2145/13 "2022-10-19T11:22:54Z")
Hey @marioreinike, Thanks for clarifying that! I’ll go ahead and update the Engineering Ticket for this issue. Please let me know if you have any questions or concerns . Best, RayanP