Topics started by Chops

4 Topics

C
Problem Solver I
ChopsProblem Solver I
asked in Developer Group

Add profiles to list failed with Invalid profile IDs: set()

I’ve been running into an issue trying to add profiles to a list in batches of 950. Things were working fine but I started to run into this error:{:success=>false, :response=>{:errors=>[{:id=>"c8932474-507f-45e6-9d12-4a1a87403ae1", :status=>400, :code=>"invalid", :title=>"Invalid input.", :detail=>"Invalid profile IDs: set()", :source=>{:pointer=>"/data/"}}]}}The endpoint is:https://a.klaviyo.com/api/lists/{id}/relationships/profiles/And I tried to keep my payload under 1000 so 950 per call.  I’ve been able to successfully move 20,000 profiles into a list without issue but lately I’ve been getting the error above.  Any ideas what might be happening?  I was going to drop my numbers down to try to isolate which profiles might be failing.  Would love any feedback if anyone has hit the same error.

4
G
Contributor I
2 months ago
C
Problem Solver I
ChopsProblem Solver I
asked in Campaigns and Flows

Filling up a date based flow for existing profiles by shifting the date

I’m working on filling up a date-triggered flow with 1000s of profiles and can’t seem to figure out why I’m not seeing the numbers I should.  I definitely am getting 100s into the flow but that’s far below what I was expecting.The flow trigger is based on their Subscription Paused Date at 12pm.  With a flow filter of Subscription Status doesn’t equal active.  Then there is a 40 day wait for the first email and 105 day for the second email, etc.And to back-fill these flows I am segmenting my profiles into lists that should be included.  Then I have a script which pulls all the profiles from those lists and updates their Subscription Paused Date minus 5 minutes.  Updates to property on a date based flow should trigger re-evaluation for the flow.  And I can definitely see that working on a small percentage of the profiles.  

7
C
Problem Solver I
11 months ago
C
Problem Solver I
ChopsProblem Solver I
asked in Campaigns and Flows

Flow filtering based on a custom property that may or may not exist

I’m defining a flow and using the flow filter as a way to limit people from getting a message later in the flow if certain conditions are met.  For example customer pauses their account they get added to the flow (which is a date based flow).  Then later they activate their account so I set a subscription_status custom prop to active.  Then I have a flow filter which says subscription_status doesn’t equal active.Some profiles won’t have this custom property set so my question, what happens to profiles that do not have this property set?

3
Irrra
Expert Problem Solver II
11 months ago
C
Problem Solver I
ChopsProblem Solver I
asked in Developer Group

Issues with invalid of unsupported phone number from the API

I’m using the latest stable API (version 2022-10-17) to create a profile and I’m running into issues with the phone number.  I understand it needs to be E.164 compliant which my numbers are, but I’m running into an issue with fake phone numbers. For example this phone number won’t work:+14161112222But this one will:+14168902222According to the E.164 guidelines both numbers should be correct.  Why is the first one failing for me?The error response is:"detail"=>"Invalid or unsupported phone number","source"=>{"pointer"=>"/data/attributes/phone_number"}And I’m using the endpoint for create:https://a.klaviyo.com/api/profiles/ 

7
A
Contributor I
1 year ago

Most helpful members this week

Terms & ConditionsCookie settings

Links & Resources

Platforms

Partners

Useful Things

About

  • Terms and Privacy
    © 2024 Klaviyo All rights reserved. Klaviyo and the Klaviyo logo are trademarks or registered trademarks of Klaviyo, Inc. or its affiliates.