Home› General

Unresolved Lots

jmpbrickjmpbrick
in General Vote Up0Vote Down
I have 476 unresolved lots that do not have a BLID to BOID match. It is causing an error when I try to sync in Bricksync.
"WARNING: No reply received for query, we will retry and later perform a deep sync.
ERROR: Too many connection errors, giving up."

Does anyone have a solution on how to clean these up?

Comments

  • 10 Comments sorted by Votes Date Added
  • StellarStellar
    edited January 2021 Vote Up0Vote Down
    That warning problem is probably related to BL being up and down yesterday and today...

    About the unmatched lots, find them in the BO catalog, submit the BL ID and in a day or so BS will start syncing them.

    And if dey do not exists (mostly stickered parts) you can create the items in the BO Catalog.
  • jmpbrickjmpbrick
    Vote Up0Vote Down
    BS was not having issues with BL. Its just when it gets to the BO sync it fails and shows a whole bunch of parts it skips. I was trying to avoid having to submit a whole bunch of ID manually and was hoping for a way to get BS to just skip those without the errors.
  • HoddieHoddie
    Vote Up0Vote Down
    I don't believe unresolved lots should cause that error. Perhaps it was just a coincidence?

    When exactly do you get that error? On start? When you manually type the sync command?
    What does the command 'owlresolve' do?
  • jmpbrickjmpbrick
    Vote Up0Vote Down
    This is what i get each time. I have also tried setting the pipeline queue to 1.

    LOG: Queued BrickOwl Query: Update item "6014bc01", color 1; Set remarks to "A112A05
    LOG: Queued BrickOwl Query: Update item "11089", color 86; Set remarks to "B101H07"
    LOG: Queued BrickOwl Query: Update item "11091", color 153; Set remarks to "B101H07
    LOG: Queued BrickOwl Query: Update item "11477pb001", color 155; Set remarks to "A108A04"
    LOG: Queued BrickOwl Query: Update item "11833", color 110; Set remarks to "D104D08"
    LOG: Queued BrickOwl Query: Update item "11833", color 34; Set remarks to "D104D08
    LOG: Queued BrickOwl Query: Update item "11957", color 11; Set remarks to "A106D03
    LOG: Queued BrickOwl Query: Update item "12939", color 103; Set remarks to "A108B06"
    10:27:24 WARNING: Error updating BrickOwl item "6014bc01", color 1.
    10:27:24 WARNING: The operation will be attempted again.
    10:27:24 WARNING: No reply received for query, we will retry and later perform a deep sync.
    10:27:24 WARNING: Error updating BrickOwl item "11089", color 86.
    10:27:24 WARNING: The operation will be attempted again.
    10:27:24 WARNING: No reply received for query, we will retry and later perform a deep sync.
    10:27:24 WARNING: Error updating BrickOwl item "11091", color 153.
    10:27:24 WARNING: The operation will be attempted again.
    10:27:24 WARNING: No reply received for query, we will retry and later perform a deep sync.
    10:27:24 WARNING: Error updating BrickOwl item "11477pb001", color 155.
    10:27:24 WARNING: The operation will be attempted again.
    10:27:24 WARNING: No reply received for query, we will retry and later perform a deep sync.
    10:27:24 WARNING: Error updating BrickOwl item "11833", color 110.
    10:27:24 WARNING: The operation will be attempted again.
    10:27:24 WARNING: No reply received for query, we will retry and later perform a deep sync.
    10:27:24 WARNING: Error updating BrickOwl item "11833", color 34.
    10:27:24 WARNING: The operation will be attempted again.
    10:27:24 WARNING: No reply received for query, we will retry and later perform a deep sync.
    10:27:24 WARNING: Error updating BrickOwl item "11957", color 11.
    10:27:24 WARNING: The operation will be attempted again.
    10:27:24 WARNING: No reply received for query, we will retry and later perform a deep sync.
    10:27:24 WARNING: Error updating BrickOwl item "12939", color 103.
    10:27:24 WARNING: The operation will be attempted again.
    10:27:24 WARNING: No reply received for query, we will retry and later perform a deep sync.
    LOG: Queued BrickOwl Query: Update item "6014bc01", color 1; Set remarks to "A112A05
    LOG: Queued BrickOwl Query: Update item "11089", color 86; Set remarks to "B101H07"
    LOG: Queued BrickOwl Query: Update item "11091", color 153; Set remarks to "B101H07
    LOG: Queued BrickOwl Query: Update item "11477pb001", color 155; Set remarks to "A108A04"
    LOG: Queued BrickOwl Query: Update item "11833", color 110; Set remarks to "D104D08"
    LOG: Queued BrickOwl Query: Update item "11833", color 34; Set remarks to "D104D08
    LOG: Queued BrickOwl Query: Update item "11957", color 11; Set remarks to "A106D03
    LOG: Queued BrickOwl Query: Update item "12939", color 103; Set remarks to "A108B06"
    LOG: Success updating BrickOwl item "6014bc01", color 1
    LOG: Queued BrickOwl Query: Update item "15068", color 3; Quantity adjust by -3
    10:27:28 WARNING: Error updating BrickOwl item "11089", color 86.
    10:27:28 WARNING: The operation will be attempted again.
    10:27:28 WARNING: No reply received for query, we will retry and later perform a deep sync.
    10:27:28 ERROR: Too many connection errors, giving up.
    10:27:28 WARNING: Error updating BrickOwl item "11091", color 153.
    10:27:28 WARNING: The operation will be attempted again.
    10:27:28 WARNING: Error updating BrickOwl item "11477pb001", color 155.
    10:27:28 WARNING: The operation will be attempted again.
    10:27:28 WARNING: Error updating BrickOwl item "11833", color 110.
    10:27:28 WARNING: The operation will be attempted again.
    10:27:28 WARNING: Error updating BrickOwl item "11833", color 34.
    10:27:28 WARNING: The operation will be attempted again.
    10:27:28 WARNING: Error updating BrickOwl item "11957", color 11.
    10:27:28 WARNING: The operation will be attempted again.
    10:27:28 WARNING: Error updating BrickOwl item "12939", color 103.
    10:27:28 WARNING: The operation will be attempted again.
    10:27:28 WARNING: Error updating BrickOwl item "15068", color 3.
    10:27:28 WARNING: The operation will be attempted again.
    10:27:28 INFO: Updating BrickOwl inventory, 10 lots to create, 332 lots to update.
    10:27:28 WARNING: BrickOwl update did not complete successfully!
    10:27:28 INFO: BrickOwl flagged MUST_SYNC for deep synchronization.
    10:30:06 INFO: Fetching the BrickLink Order List...
    10:30:10 INFO: We are up-to-date on BrickLink orders.
    10:35:09 INFO: Fetching the BrickOwl Order List...
    10:35:12 INFO: We are up-to-date on BrickOwl orders.
    10:35:12 INFO: BrickOwl is flagged MUST_SYNC for deep synchronization in 1331 seconds.
  • HoddieHoddie
    Vote Up0Vote Down
    I'm not sure how or why but BrickSync is trying to update something that doesn't exist. It thinks you have a lot of 11089 in Sand Purple, and is trying to update the remarks of said lot. It looks like BO isn't returning an error, or BrickSync is misinterpreting it somehow.

    I would manually add the 11089/Sand Purple lot to your BO inventory, and see if BrickSync still trips over it.

    You could also try the 'sync brickowl' command to see if that helps.
  • beaverbrickbeaverbrick
    Vote Up0Vote Down
    @jmpbrick

    The colours look OK to me.

    Those errors look like some sort of connection/comms issue.
    Has BrickSync previously been working fine and this just suddenly started happening?

    Type "status" into the BrickSync window and look for any obvious issues in there, but check the "BrickLink/BrickOwl API usage" (near the bottom).

    Also type "verify" into the BrickSync window. This will list the differences between locally tracked inventory and BL/BO, without making any changes.
  • beaverbrickbeaverbrick
    Vote Up0Vote Down
    @jmpbrick

    Also, how many tracked items are in your inventory? It shows you under the status command.
  • jmpbrickjmpbrick
    Vote Up0Vote Down
    @beaverbrick

    So it just started happening yesterday. My inventory levels shouldn't be an issue as they are at only 155K. the API usage tho concerns me. BL is at 358 but BO is at 4554. Would that cause am issue?
  • beaverbrickbeaverbrick
    Vote Up0Vote Down
    @jmpbrick

    Yeah that API usage sounds high.
    I don't know the API limits here on BrickOwl, whether it's a daily limit or possibly a per-minute type limit.
    Maybe @Lawrence could confirm?

    Inventory levels should be fine... BrickSync used to have a 250k limit for unregistered accounts, but looks like that limit has been removed anyway.
  • StellarStellar
    Vote Up0Vote Down
    @beaverbrick 600 api calls per minute:

    https://www.brickowl.com/api_docs
Sign In or Register to comment.