You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Hope you're having a great time at .all - no urgency on this!!)
I have noticed with Craft 4 / Campaign 2 (up to date with both) - that our Campaigns no longer send in the same order as they used to - they used to send to the oldest contacts first (i.e. starting with me, user 1) - but I am not quite sure what the order is now, seems basically random.
I definitely preferred the older behaviour (and it meant our oldest customers were rewarded by getting notice of specials slightly before others etc) - and am wondering why this change was made, and if there is some chance it could be reverted (even if optionally) - to restore the old behaviour.
Thanks Ben!
The text was updated successfully, but these errors were encountered:
Thanks for your understanding. I agree that the order should be more deterministic and will look into what changed and see if I can resolve for the next release.
I’ve made it so that pending contacts are fetched in order of their ID, which should correspond to oldest first, in 42668c2. You can test this by running composer require "putyourlightson/craft-campaign:dev-develop as 2.8.8".
(Hope you're having a great time at .all - no urgency on this!!)
I have noticed with Craft 4 / Campaign 2 (up to date with both) - that our Campaigns no longer send in the same order as they used to - they used to send to the oldest contacts first (i.e. starting with me, user 1) - but I am not quite sure what the order is now, seems basically random.
I definitely preferred the older behaviour (and it meant our oldest customers were rewarded by getting notice of specials slightly before others etc) - and am wondering why this change was made, and if there is some chance it could be reverted (even if optionally) - to restore the old behaviour.
Thanks Ben!
The text was updated successfully, but these errors were encountered: