Content Delivery API's `total` property includes documents in the recycle bin

[liamlaverty]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

V13.1.1

Bug summary

In the Content Delivery API, when making requests to the PagedContent API endpoints, the returned object contains a property total. The total property includes all of the content published in the site and sometimes includes recently deleted content, until the examine index is rebuilt.

Specifics

http://localhost:59970/umbraco/delivery/api/v2/content?skip=0&take=10&fields=properties%5B%24all%5D

See screenshot attached. The total property counts 6 items, while the items array includes only 5 elements. The final unlisted array element is in the website's recycle bin.

Steps to reproduce

• In a fresh Umbraco install, create a piece of content in the application
• Query the endpoint /umbraco/delivery/api/v2/content?skip=0&take=10&fields=properties%5B%24all%5D
  • receive a result with total: 1, and an array of 1 items
• Delete the piece of content from the application
• Re-query the endpoint
  • receive a result with total: 1 and an array of 0 items
• Rebuild the examine index, then re-query the endpoint
  • receive a result with total: 0 and an array of 0 items

Expected result / actual result

Expected result: the total to match the number of items available in the API

Actual result: the total matches the number of items in the Examine Index, which includes recently recycled items

[github-actions]

Hi there @liamlaverty!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[elit0451]

Hey @liamlaverty 👋

Thanks for pointing this out 💪 I can confirm this is an issue only in v13.

[kjac]

Fixed in #15848 😄