Hey @Lo2024 

The issue you're experiencing with the ScheduledEstimate property defaulting to 0 instead of updating to Yes in Klaviyo is likely due to how the data is being sent and interpreted by Klaviyo.

Ensure that the data type for the ScheduledEstimate property is consistent. If Klaviyo is expecting a string but receives a numeric value (or vice versa), it could cause issues.

Double-check the API call you're making to update the property. Ensure that you're sending the correct payload and that the ScheduledEstimate value is being passed as "Yes" and not 0. Here's an example using cURL:

curl -X POST \
  https://a.klaviyo.com/api/v2/list/YOUR_LIST_ID/members \
  -H 'Content-Type: application/json' \
  -d '{
    "api_key": "YOUR_API_KEY",
    "profiles":  
      {
        "email": "example@example.com",
        "properties": {
          "ScheduledEstimate": "Yes"
        }
      }
    ]
  }'

Note - If ScheduledEstimate is also being set or updated elsewhere in your integration, this could cause conflicts. Make sure the property is being managed consistently across your entire setup.

If this still doesn’t solve your issue, then I would suggest you contact klaviyo support. They can offer more specific guidance and troubleshoot any backend issues.

I hope this helps

Cheers and thank you for being part of this amazing community. 

Arpit Banjara