tmilar/meli-manager

When two or more notifications of a same new order arrive (almost at the same time), duplicated rows are written.

Closed this issue · 2 comments

Sometimes, when more than one notification for one (not yet stored) Order are received, both are written in spreadsheet almost simultaneously, which leads to duplicated row

Possible solution:
Serialize the spreadsheet writing requests to prevent duplicated entries. For example, by enqueing the writing requests, then writing one at a time. Or at least one at a time per resource (order) id.

This is happening because of two same order notification topics arriving: 'order' and 'order_v2'. Decide on which one to use and leave the other out... Or find another way to prevent duplicated entries.

Fixed by removing Application topic 'orders', now keeping only topic 'orders_v2' and seems to be working fine.