You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our db and servers are set for America/New_York timezone.
We are getting the error below:
Illuminate\Database\QueryException · SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '2025-03-09 02:35:01' for column 'ends_at' at row 1 (Connection: erank_main, SQL: update `subscriptions` set `ends_at` = 2025-03-09 02:35:01, `subscriptions`.`updated_at` = 2025-02-09 20:16:28 where `id` = 107213)
But the time that's getting written doesn't exist because it jumps from 2am to 3am on March 9, 2025.
Since this is getting written by the Laravel Cashier system, we have no way to fix this short of reconfiguring our db to allow invalid dates, which isn't a solution.
Steps To Reproduce
Send the following payload to the paddle/webhook endpoint:
Err I'm not sure what we should do here. This is a datetime we receive from Paddle. 2024-07-03T02:03:15.051183Z isn't something we control. What should we change it to? 1am? 3am? I don't feel we should be responsible for controlling that. Paddle should not send invalid datetimes.
I'll contact them but they will tell us that their webhooks come in in UTC timezone. But if we have our db set to ET something somewhere needs to convert the date. I would think that Cashier would convert UTC to the server/db timezone. Since we can't modify your code due to being under repo, we can't make any adjustments or intercept the webhook data prior to being written.
Cashier Paddle Version
2.5.6
Laravel Version
11.41.3
PHP Version
8.3
Database Driver & Version
MySQL 8 on Amazon RDS
Description
Our db and servers are set for America/New_York timezone.
We are getting the error below:
But the time that's getting written doesn't exist because it jumps from 2am to 3am on March 9, 2025.
Since this is getting written by the Laravel Cashier system, we have no way to fix this short of reconfiguring our db to allow invalid dates, which isn't a solution.
Steps To Reproduce
Send the following payload to the paddle/webhook endpoint:
Mysql will throw the error if your db is in a timezone that recognizes daylight savings time:
The text was updated successfully, but these errors were encountered: