#tyler_api

1 messages ¡ Page 1 of 1 (latest)

crystal oarBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1356688030814965810

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

chrome terrace
#

Hi there - having a look

sweet dune
#

Oh, does it use the timezone configured for the account? Maybe I should set that to UTC?

chrome terrace
#

hmm

sweet dune
#

The Stripe times seem off. Looking at this log message:

2025/04/01 18:45:47 Received GitHub webhook event type: pull_request
[ERROR] Request error from Stripe (status 400): {"status":400,"message":"The event timestamp cannot be in future. Expected a timestamp less than or equal to 1743520160.","request_id":"req_IvYOdLGSyo9pTn","request_log_url":"https://dashboard.stripe.com/test/logs/req_IvYOdLGSyo9pTn?t=1743529548","type":"invalid_request_error"}
time=2025-04-01T18:45:48.398+01:00 level=ERROR msg="error handling task" task_id=2953 error="error creating meter event: {\"status\":400,\"message\":\"The event timestamp cannot be in future. Expected a timestamp less than or equal to 1743520160.\",\"request_id\":\"req_IvYOdLGSyo9pTn\",\"request_log_url\":\"https://dashboard.stripe.com/test/logs/req_IvYOdLGSyo9pTn?t=1743529548\",\"type\":\"invalid_request_error\"}"
chrome terrace
#

the timestamp you sent is 1743529548 and we say we expected something less than 1743520160

sweet dune
#

Oh, nevermind

#

I was looking at a old one.

#

So, looking at req_IvYOdLGSyo9pTn

#

The Stripe UI is showing the time of that event happening at UTC 5:45:48 PM Apr 1, 2025

#

The error gives says it needs to be before 1743520160, which is April 1, 2025 3:09:20 PM UTC

chrome terrace
#

Yeah, that's right. Testing to see if I can reproduce this

sweet dune
#

Thanks

chrome terrace
#

Ah, you're using a test clock

sweet dune
#

Ahhh

#

And it's frozen in time

chrome terrace
#

Yep! For testing you could just omit timestamp and it would use the frozen time of the clock

sweet dune
#

Oh, I didn't realize it was optional

chrome terrace
#

Or you could retrieve the clock and look at the frozen time immediately before creating the meter event

sweet dune
#

I think I will just omit if there is a test clock

#

Thanks so much!