Appearance
Deal with set-aside messages
You get changes that Stock Sync set aside in the outbox moving again, once the technical team has fixed what stopped them.
Before you begin
Who can do this: anyone can look; releasing needs an Operator. Viewers see the list without tick boxes or Release buttons.
Time needed: 2 minutes to report, 1 minute to release once the cause is fixed.
Before you start: understand what a set-aside message is. Every change inside Stock Sync (a new stock number, a published quantity) is first written to the outbox, then handed to the internal message queue. If the queue refuses a message 5 times while it is accepting other messages, Stock Sync sets it aside so it does not block the others. A set-aside message never moves on its own. See The outbox.
Fix the cause first
The reason is always technical (the queue is set up wrongly, or down). Releasing a message before the technical team has fixed it only sets it aside again, within seconds, after 5 more refusals.
Steps
Notice the signal. Any of these means something is set aside: a red number beside Activity in the sidebar, a red number on the Outbox tab of Activity, or the red row [n] outbox messages set aside in the Overview's Needs your attention.
Open Activity and click the Outbox tab (or Review on the Overview's row, or Ctrl K and Outbox).
For each message, read Set aside (when), Account, Change (what kind), Refusals and Reason. Refusals counts every refusal, the one that set it aside included, so a message set aside after five refusals shows 5, and one set aside at once without ever being refused (for example because it is too large) shows 0. Hover over a column's ⓘ for what it shows.
Change is the technical name of the kind of change: offer.stock-changed, for example, is a new stock number for an offer. The Reason is the queue's own error, such as NO_ROUTE (the queue has nowhere to deliver this kind of message). You do not need to understand it; the technical team does.
Send the list to the technical team: a screenshot, or the account, time and reason of each line. Wait for them to say the cause is fixed.
To release one message, click its Release button.
A dialog asks Release this message?: "It goes back among the pending changes and the relay tries to publish it on its next tick. Fix the cause first, or it is set aside again." Pending changes are the messages waiting to be handed on; the relay is the part of Stock Sync that hands them to the queue, a few times a second (each round is a tick); to publish here means to hand on.
Click Release.
To release several messages, tick them (Shift + click ticks a range) and click Release ([n]) on the bar at the bottom. The dialog asks Release [n] messages?; click Release.
To release every message of one account at once, choose the account in the Account filter chip. Release all for [account] appears beside it.
Click Release all for Fashion Days RO. A dialog asks Release every set-aside message of Fashion Days RO?
Click Release all. It releases every set-aside message of the account, including any beyond the 50 the list shows.
What you should see
- The message: "Released 1 message. The relay tries it again from its next tick." (or "Released [n] messages. …" after releasing several or Release all).
- The message leaves the list at once, and the red numbers beside Activity, on the Outbox tab and in Needs your attention go down.
- The relay tries the message within a second. If it goes through, the change it carried carries on: offers it concerned become In sync within a few seconds on a sending account.
- The account's Activity tab records the release.
- When nothing is left, the tab says "Nothing is set aside. Every change reached the queue."
If something goes wrong
| You see | Do this |
|---|---|
| The released message comes back soon after, set aside again | The cause is not fixed. Tell the technical team; do not release again until they confirm. |
| No set-aside outbox message has id … or "Nothing was released: 1 message had already been released." | Someone released it already. Nothing to do. |
| No outbox message of [account] has been set aside | Someone released them already. |
| "Showing the newest 50 of … set-aside messages." | The list shows at most 50. Choose the account in the Account filter and use Release all, which releases every one. See the picture below. |
| No Release buttons | You are a viewer. |
| Pages show "Connection lost …" or Not live, and the message queue is down | Changes wait and go out when it is back; nothing is set aside for that. Tell the technical team. |
The note "Showing the newest 50 of 73 set-aside messages." means the list stops at 50; the total is the same as the red number on the Outbox tab (73 in the picture) and beside Activity.
See also A message is set aside in the Outbox.
Example
At 09:48 an update of the message queue goes wrong: it no longer knows where to route some stock changes. The relay's tries are refused, and after 5 refusals each, three messages are set aside, two of Fashion Days RO (at 09:50 and 09:51) and one of eMAG RO (at 10:14), each with the reason "Refused 5 times; last: Error: NO_ROUTE - no queue bound for routing key …". All other changes keep flowing.
At 10:52 Radu sees a red 3 beside Activity in the sidebar, and 3 outbox messages set aside in Needs your attention. He clicks Review, takes a screenshot of the Outbox tab and sends it to the technical team. At 11:20 they reply that the queue is fixed.
- He clicks Release on the eMAG RO message and confirms: "Released 1 message. The relay tries it again from its next tick." The red count drops to 2, and the message does not come back.
- He chooses Fashion Days RO in the Account filter, clicks Release all for Fashion Days RO and confirms: "Released 2 messages. …" The tab now says "Nothing is set aside. Every change reached the queue."
Had anyone released them before the fix, they would have been set aside again within seconds, with the same reason. That is why the fix comes first.
Related
- Activity → Outbox: the tab explained.
- Sending stock to the marketplace.
- Messages and what they mean.