---
# System prepended metadata

title: Brickscout - Tech Report 5

---

# Brickscout - Tech Report 5

### 1. Unavailable Items Missing Information
Fetching cart_bulder entries, products that are not available have missing
properties needed to display product information accordingly. Mainly EAN
which is used to fetch item information (images, name, etc.).
```
...,
"eansNotFound": [
    {
      "neededQuantity": 1,
      "condition": null,
      "quantityType": "NOTHING"
    },
    {
      "neededQuantity": 1,
      "condition": null,
      "quantityType": "NOTHING"
    }
  ],
...
```

### 2. Fetching Shop Icons
Fetching shop images (logo) is resulting with 403 error. This makes it 
impossible to render cart_builder properly.

### 3. Subsequent Requests for CartBuilder
Fetching cart_builder entries by UUID for the second time results in 409 
error. This is a GET request and receiving IntegrityViolation upon insertion 
seems odd. If this is lazy loading data for cart_builder, please consider
having check if cart_builder entries data has already been populated.

This error means that once on the cart_builder page has loaded, user can not 
refresh the page.

### 4. Fetching cart_builder entries sometimes fails
Fetching cart_builder entries sometimes takes a long time and results in 500
error.

I'm providing request data so hopefully you can find the issue in your error 
logs. 

Example of a request that failed:
```
Request: 

Request URL: https://api-acc.brickscout.com/api/core/users/Testdirk7/cart_builder/088236c4-131d-4acf-928f-74b80a99e2a7/entries
Request Method: GET
Status Code: 500 
Remote Address: 18.193.22.202:443
Referrer Policy: strict-origin-when-cross-origin

Response:
{
    "type":"UnknownException",
    "exceptionCode":0,
    "developerMessage":"It's looking like you may have taken a wrong turn. Don't worry...it happens to the best of us.",
    "moreInfoUrl":"/api/docs/errors/0.html",
    "timeStamp":1622794332323
}
```

Additional troubleshooting information:
If user tries fetching cart_builder entries, and it is taking a long time
and then tries navigating back to wishlist page, that requests also hang 
until the previous requests finishes processing (with 500). As soon as 
prev requests fails completely, wishlist performance is back to normal.

This probably indicates resource intensive queries on cart_builder/entries 
endpoint - which would seem plausible given previous (#3) problem described
above.

### 5. cart_builder returns empty responses
![](https://i.imgur.com/H69iJuR.gif)

(gif link: https://i.imgur.com/H69iJuR.gif)

This issue seems to happen after previously described error starts 
happening.

