Hi brainCloud team,

We are seeing an issue where an Automated Promotion that previously worked correctly no longer activates under the same conditions.

The promotion we are testing is configured as follows:

App ID: 15389 Promotion ID: 6 Promotion Type: Automated Promotion Applicable members: currently set to Both existing and new entrants to the segment Target Segment: XP level based segment

This promotion was configured about a month ago, and from the beginning its Applicable members setting was New entrants to the segment only. It previously worked correctly with that setting.

Previously, when a new user progressed in the game and newly satisfied the XP level condition for the target segment, the Automated Promotion became eligible and was shown correctly on the client.

Recently, however, the promotion no longer activates with the same setting and the same flow. We have currently changed it to Both existing and new entrants to the segment as a temporary workaround for testing.

Current reproduction flow:

Start with a new user The user starts in a state where they do not satisfy the target segment condition The user progresses in the game and satisfies the XP level condition In the brainCloud console, the user is confirmed to be included in the target segment However, Promotion ID 6 does not appear in Eligible Promotions If we change the same promotion’s Applicable members setting to Both existing and new entrants to the segment, it immediately becomes eligible

So it looks like the user is correctly entering the target segment due to an XP level change, but the Automated Promotion is not being associated/activated when using New entrants to the segment only.

We also noticed this related forum thread mentioning a similar issue and a patch:

https://forums.getbraincloud.com/topic/355/automated-promotion-not-associated-for-users-already-in-target-segment

Could you please confirm the following?

Is New entrants to the segment only expected to activate when a user newly satisfies a segment condition due to an XP level change? Since this used to work before but no longer works with the same configuration and flow, could this be related to a recent patch or a change in promotion/segment association logic? After updating XP level, is there any additional refresh or reevaluation step required besides calling RefreshPromotions? As a workaround, Both existing and new entrants to the segment works. Is this the recommended setting, or should New entrants to the segment only still work for this case?

Thank you.

Added the additional details to 13660

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.