Thank you! I used the following query to find out the reason: however,  actionName is blank and execution_count has 7 times unable to be linked which action nodes generated 7 times. why is that? and how come it was triggered 7 times instead 1 as the profile is unique flowing into one branch to the a...

Hi Team,We’re using a custom action in the journey to trigger an HTTP call to a downstream API service, which transfers journey data to a third-party system.I’ve ensured that all journey data is unique, with no duplicates on our end.However, upon reviewing the data in the third-party system, we’ve n...

Thanks a lot! quick question that they're blocked at exit criteria looks like. my entry audience are batch evaluations run every 24 hours that should have removed bad profiles at audience level. why they're excluded even on the journey level with exit audience?

Hi Team, After running a journey in AJO and reviewing the "All Time Report," I noticed that some records were excluded under the Journey Exclusions section with the reason:ERROR_SEGMENT_REALISATION_CONDITION_MISMATCH.However, it's unclear what exactly caused these records to be excluded. Could you p...

I did not try with specific date as it's out of scope. I would compare two attributes that's the point. thank you.

Hi,I tried another way having the same results with even more estimated profiles up. It seems not right as long as with two date fields make the comparison. I totally lost the how the audience behaves now. please advise what's the reason you recommended in that way and next step.

In Adobe Journey Optimizer (AJO), I'm defining an audience using a rule where:registration_date <= expect_date - 3 months. The format of the registration_date is:2025-03-10T14:43:57Zand the format of the expect_date is:2025-06-03T00:00:00Z.This means that expect_date - 3 months evaluates to approxim...

Got it. see above the test profile qualifies in both audiences in green

 not sure if you are looking for above.  I tested 3 scenarios: use case 1:it tells me the order of path in the condition node is take precedence regardless of level of placement in the canvases use case2:it tells me the order of condition node does not matter is dependent on the placement level in t...

this test profile qualifies both paths for sure