Queue Processing Best Practices

How To
,
1

I’m helping a client process data that piled up in a scenario’s queue after an error shut it down. We’ve resolved the error, and now I’m thinking about risks in how we process the old data. I’m worried that if the scenario didn’t default to processing the earliest queue records first, it may have overwritten more recent data with outdated data (it’s watching Sheet changes and updating Hubspot). I looked in help and partner training and wasn’t able to quickly find a mention of queue processing order following a first-in, first-out (FIFO) or last-in, first-out (LIFO) order, so I thought I’d ask here.

Thanks!

2

You may wait until you get more input before making a decision, but I believe in this situation:

  • The items in queue remain in the order in which they were added.
  • If you were to change the scenario now to enable Sequential Processing, then it should run one after another, in order, until all caught up.
  • Basically anything currently in the queue will according to how the scenario is currently configured, not how it was when the item was originally added.

Again, I hope others can help confirm or correct, but I that that’s how it would work… Good luck!

4 Likes