Hello!
To use the forum, login or register above.
(If you are already logged in above, please click here)
BrickSync - How to fix BO/BL catalog mismatch
Hi,
I've had this problem before, where there's some kind of mismatch between BrickLink and BrickOwl, and BrickSync is unable to create the lot in BrickOwl. This manifests itself with an error during a "sync", and in my case I'm getting this:
WARNING: BrickOwl HTTP Error - Saving server reply (422+47 bytes) at path "data/errors-2018-12-31/00498.txt".
WARNING: Error creating BrickOwl item "bb787c02pb01", color 2.
WARNING: It's possible we may have cached an old BOID for this BLID. Try updating the BLID<->BOID translation cache by typing owlqueryblid -f bb787c02pb01.
WARNING: The operation was rejected by BrickOwl. A further sync will attempt the operation again.
The error log file contains the HTTP headers and this:
==== DATA ====
{"error":{"status":"Lot could not be created"}}
==== END ====
The IDs for the items in both catalogs seem to be correct.
In the past, when I mentioned a similar issue, someone went and fixed something in the catalog, and BrickSync was able to work its magic after that.
Now I'd like to know what fix was applied, so I can do it myself when needed.
Can someone help?
Thanks in advance!
I've had this problem before, where there's some kind of mismatch between BrickLink and BrickOwl, and BrickSync is unable to create the lot in BrickOwl. This manifests itself with an error during a "sync", and in my case I'm getting this:
WARNING: BrickOwl HTTP Error - Saving server reply (422+47 bytes) at path "data/errors-2018-12-31/00498.txt".
WARNING: Error creating BrickOwl item "bb787c02pb01", color 2.
WARNING: It's possible we may have cached an old BOID for this BLID. Try updating the BLID<->BOID translation cache by typing owlqueryblid -f bb787c02pb01.
WARNING: The operation was rejected by BrickOwl. A further sync will attempt the operation again.
The error log file contains the HTTP headers and this:
==== DATA ====
{"error":{"status":"Lot could not be created"}}
==== END ====
The IDs for the items in both catalogs seem to be correct.
In the past, when I mentioned a similar issue, someone went and fixed something in the catalog, and BrickSync was able to work its magic after that.
Now I'd like to know what fix was applied, so I can do it myself when needed.
Can someone help?
Thanks in advance!
Powered by Vanilla
Comments
@Moc Magic Bricksync can only synchronise items of which the BLID is known on BO. For mostly decorated items this implies the BLID must be submitted on BO. You can pull a list from your Bricksync log (take yesterdays for startes) and check for 'Failed BOID lookup for' lines.
I notice I have plenty myself, a quick view tells BL has once again added a 'zero' on many decorated items.
BL example: Changed Item No from {50955pb15} to {50955pb015}
The new number is unknown on BO and requires an update.
BL has the nasty habit of doing so, extremely annoying.
If I have time tomorrow, I'll go over recent changes, and submit the updates for full sections.
Updating the number above is not enough, the entire line must be done
so from 50955pb01 > 50922pb31 everything must become 50955pb001 >50922pb031
The easiest way to do so is by generating a file to be read by BS...
BTW: Be ready for loosing all SW figs on BO, BL just reached n°1000, I consider it very likely they will be renumbering all SWxxx numbers into SW0xxx shortly. If I have the time next week I'll submit a file to preventively add the extra 'zero' on each older SW fig to prevent 'non sync' when BL decides to change them (BO can hold both the old and new number)
> @brickrepository The BLID has been incorrectly attached to the color TAN, in stead of the uncolored 'parent' version. I've made the submission on the parent now. When @lawrence approves, this should start to sync correctly. Such a submission error is hard to figure out trough BS, so you can always include me in such messages to have a deeper look.
Thanks!
I think I understand what the problem was... But if I run into any of these issues I might have to ping you to have a look.
Good call on that re-numbering of the SW figures. It's a good idea to let @Lawrence know in advance so that when the change happens on BL, the BO catalog can be updated quickly.
And on that same note... 1000 unique Star Wars minifigures?! WOW!
WARNING: Error creating BrickOwl item "bb787c02pb01", color 2.
WARNING: It's possible we may have cached an old BOID for this BLID. Try updating the BLID<->BOID translation cache by typing owlqueryblid -f bb787c02pb01.
WARNING: The operation was rejected by BrickOwl. A further sync will attempt the operation again.
Also got a new one:
WARNING: Error creating BrickOwl item "22385pb017", color 18.
WARNING: It's possible we may have cached an old BOID for this BLID. Try updating the BLID<->BOID translation cache by typing owlqueryblid -f 22385pb017.
WARNING: The operation was rejected by BrickOwl. A further sync will attempt the operation again.
Any ideas @robernat ?