Hello brainCloud team,

Thank you for the clarification. That explanation helps us understand the current behavior.

We would like to add more detail about our current situation, because the issue we are seeing is not limited to users who were already in the segment before the Automated Promotion was created.

We created a new Automated Promotion and attached it to a target segment. After that, we had a user who was not previously in that segment become eligible by updating the relevant user statistic. After calling RefreshMySegments, the user appears in the target segment under User Monitoring > Pricing.

However, the promotion still does not appear under Associated Automated Promotions for that user, and GetEligiblePromotions / RefreshPromotions do not return it.

The promotion only starts being associated and returned after we manually use Reset Segments / re-evaluate segments for that specific user from the portal.

So the issue appears to be:

The user is newly entering the segment after the Automated Promotion has already been created and attached. RefreshMySegments updates the user’s current segment membership correctly. But the Automated Promotion is not associated with the user. A manual per-user Reset Segments / re-evaluation from the portal makes it work.

Could you advise if there is any supported workaround for this before the planned fix is released?

Specifically:

Is there any Cloud Code, client, or S2S API equivalent to the portal Reset Segments / per-user re-evaluation action? Does RefreshMySegments trigger the same enteredIds logic that Automated Promotions use, or does it only update the user’s current segment membership? If RefreshMySegments does not trigger Automated Promotion association, what is the recommended way to launch a new Automated Promotion and have it apply to users who become eligible after launch? Is there any safe operational workaround that does not require manually resetting segments for each user? Do you have an estimated timeline or release version for the planned fix?

Our current blocker is that even newly eligible users for a newly created Automated Promotion are not receiving the promotion unless we manually reset/re-evaluate segments per user, and we need a scalable way to handle this.

Thank you again for your help.

we are currently developing an automation that checks some BrainCloud content using a Slack bot.
The current system of receiving PDFs via email cannot resolve this issue.
It would be great if we could retrieve the contents of PDFs regarding dates and durations using a REST API.
(To be precise, I need to receive the content included in the PDF as text.)

Q1: The removed player is completely excluded from reward calculation, so if the deletion happens before the job runs, that player is never iterated over and receives no rank or rewards.
Q2: Yes, the modified score will be used. The job always reads live state. Note that whether the score actually gets modified depends on the leaderboard type (e.g., for the LOW_VALUE type, only updates if the new score is less than the existing)
Q3: No backfilling, the next joiner goes to the latest instance, not the freed spot in ^2. No loop over earlier instances (^1, ^2) ever happens. The next joiner goes to ^3 (or ^4 if ^3 is full). The freed spot in ^2 stays empty permanently.

brainCloud developers have just release several playable builds of our famous examples! See our cool features in action. Find them at https://getbraincloud.com/demos for Windows, Mac, online and mobile.