I’m consistently receiving 500s when trying to create a date-triggered flow using either the “Created” or “First Active” property. This might apply more broadly for any date-triggered flow but I can’t say for sure.
Repro steps
1. Create a date-triggered flow in the UI using “Created” or “First Active” as the trigger. No need to add anything else
2. Navigate to the JSON view of the flow, by deleting /edit from the url and adding .json in your browser URL bar.
3. Copy/paste the payload into Klaviyo’s 2025-10-15 Postman Collection request for Create Flow.
4. Delete all attributes except name + definition. Remove relationships + links fields. Update “id” on the one action to “temporary_id”
5. Send the request and receive a 500
Here’s an example error ID I received: cb548db8-ba0d-47eb-874d-e3e35e33cf57
Receiving 500s when creating date-triggered flows via the API
+12+12
- cases 1 and 2 would result in a 400 error response, and neither is applicable here
- case 3 would likely result in a 4xx error
- case 4 is the only one that is semi-relevant here; however 500s are rarely transient, and typically indicate a real unhandled error on the server side. 502 and 503 might be transient and could be retried.
I’m confident this is an unhandled error on Klaviyo’s side vs. a simple mistake on my side
+28Hi
Just reached out to our engineers and let them know the steps you took, so they can replicate this and investigate the issue. I’ll reach back out with an update.
+28
We’ve logged this as a bug, and are working on a fix!
+12Thanks for the update,
Log in to the Community
Use your Klaviyo credentials
Log in with Klaviyo
Use your Klaviyo credentials
Log in with KlaviyoEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.