Thanks, exactly So if you check in the schema this 64-character limit is not present for the field treatment name I was trying to look at other field limits but it seems like there is no limit establish

In that section an error pops up and doesn't save,  Please save it with the correct name and then go to edit the email,  on the left side of the screen the you will see 2 treatment names, try to modify from there but it is not working 

If I check by treatment name it mentions no limit But when I fill in the title I see there is actually a limitso this is information is not really matching

Hey @DavidKangni Sorry, but Im actually looking for the character limit when you create an audience in AEP or you create a Journey/Campaign   

We are setting up some internal naming conventions and Im not able to find any limitation in terms of characters length for the following Journey NameCampaing NameDelivery/Action NameAudience Name For exampleTreatment Name -> 64 Characters Limit

@MrMAK coming back with something that might be better for you. Do you have this dataset available on your end? JOJourneyVersionsDsThis dataset contains all the details you are looking for

Have you check that the profile have the correct attributes updated?  Follow this steps and you should be able to send a proof to test the landing pagehttps://experienceleague.adobe.com/en/docs/journey-optimizer/using/test/preview-test/test-profileshttps://experienceleague.adobe.com/en/docs/journey-...

Are you using the correct identity to match the value you are using? seems like there is an issue with the profile you are testing with.  Does your profile have an attribute -> testprofile = true?

@Caveman77 in this case if you need audience counts at the moment, and as mentioned by others. You will have to run a query to get them at the moment and you don't need to wait the 24h for the audience evaluation

Description - One-off Journey status behavior Why is this feature important to you - This way we will maintain the total amount of journeys live reduced cause usually users forget to stop it or close it and that causes to reach the limit of the total live journeys. Also, when working on the same pla...