Promotion Bucket - Siebel Loyalty

Hello,

We have a promotion rule which uses promotion bucket to store the transaction number. This number is used by a scripted custom action to get the expiry date of the transaction. The custom action then copies this date from the transaction number obtained from the promotion bucket and sets it on the Accrual item. However, we have noticed that if there are a lot of transactions created for the same member id in a very small time interval, the loyalty engine shares the promotion bucket record for multiple transactions created at the same time. Hence the transaction number gets over