I personally haven’t gotten any response from Bubble team in about 3 days now.
1 Like
I received a response from the Bubble team, and they mentioned that they are working on the issue. However, the delay in resolving this problem is very discouraging, especially considering that 24 hours have passed since their reply to me, and several days since the issue first appeared.
1 Like
Oh no - I am impacted also. Support ticket going in.
For everyone on the thread I encourage you to put in a support ticket to get Bubble’s attention.
1 Like
Ticket response
Hello,
This is Ranne from the Bubble Support Team. Thank you for bringing this to our attention.
I’ve been able to confirm that other users are experiencing this behavior, and our engineering team is currently investigating the issue. Our team will be in touch directly once it is resolved.
Thank you for your patience, and understanding.
3 Likes
this should now be resolved
Hi everyone, looks like the engineering team deployed a fix for this a couple of hours ago. Let me know if the issue persists
4 Likes
Thank you for looking after us @fede.bubble 
1 Like
@courtlend engineering is telling me the issue is fixed as far as they can tell. I’m not sure if this is just the fix needing time to propagate or if they missed anything.
Are you seeing the exact same issue as the one described in the thread? or is it new (slightly different)?
It must have been a small, delay just refreshed again and now it appears to be working fine!!!
1 Like
Yep, it definitely works now. Thank you bubble devs for quickly resolving this.
Surely by now (6+ hours later) it should be fully propagated, yet I’m still seeing the issue with my ultra-simple API test data…
{
"date_item" : 1737239896,
"date_list" : [
1737239896
]
}
Am I just being a bonehead and overlooking something obvious? 
Is your app on scheduled or immediate releases? If Scheduled, this would propagate to you overnight (~9 AM ET)
Immediate. It’s a free plan. I use the app exclusively for bug testing. Maybe it’s an edge case that was overlooked?
EDIT
And oh yeah, it’s the test version of course, since I can’t deploy to live on the free plan. I wouldn’t expect any difference between live and dev though. Then again, there’s this thread (which may or may not be related).
Thanks for resolving it.
Is there something we can learn/do to have such bugs resolved more rapidly?
On our end, 4 days after the first bug reports seems too long. We weren’t even waiting for the fix anymore as we had to implement workarounds ourselves.
I also think the behavior of this API response field type should be in Bubble’s doc.
Let me know if I missed it in the documentation, but as far as I know the only place where you learn that date (UNIX) converts second timestamps into a bubble date is in the forum.
In this post from 2021: Timestamp convertion to Date(UNIX)
And now in this thread…
1 Like
This bug created a recursive loop in my app… Result: 1M workload units.
So I asked the support team to refund me the workload units, but they wouldn’t refund me. Same here. My app was working just fine, until one day, when I wake up, I see all these alert emails about workload spikes on my app. Unacceptable to let me pay 1M workload units and not refund me @emmanuel
After my emails asking for a refund, here’s the final message I got about my request:
1 Like
This topic was automatically closed after 14 days. New replies are no longer allowed.