|
TTBC
|
November 30, 2021 at 3:56 pm
Hi,
I also have a set of bad dates where it appears to be making the REG_date in the API be in the future and the REG_date_gmt to be the local Sydney time when the ticket was created.
Can you explain why this is happening as it is not just a one-off occurrence?
This is messing with our API imported as we are using the reg date as the reference to obtain the newest records each time we fetch a new set of registrations. Hence sometimes the GMT is correct so the ticket is missed as it goes back to the correct time. eg Australia/Sydney -11 hours to get GMT. While other times EE is storing the Australia/Sydney time, not the GMT date.
SCREENSHOT OF POSTMAN API FETCH
AS you can see from my laptop Pacific/Auckland time in the attached link
|
