12/12/2024 - Pepper: Priority processing Orders first

Integration suffers when the number of actions or contacts fetched for an account spikes. Work done ensures processing of the most critical data first. Some dynamic field data is not making it through

🐛 Bug Fixes

1. Strict order is defined for priority actions

2. Resistant to user error, such as duplication or placing configured actions in the wrong order

3. Each type of action we fetch is processed asynchronously as we move to process the next

4. During the bulk fetch of contacts, if the hard limit is reached, then fetching of contacts will stop and fetching of the first group of actions will begin

5. General code refector reduces loops / improves efficiency

6. Mapping no longer filter out perks ( actions ) the have zero `pointsAvailable`. All instances of points balance adjustment will now be recorded

👨‍💻 Lee