Issue Summary

When performing a content fetch API call with `expand=metadata.labels` option, the `metadata.labels.results` comes back empty for some results. It can be reproduced reliably by setting `limit` to a high number (ex: 200) and `start` value of 0.

Steps to Reproduce

1. Setup Confluence Cloud connect app with custom content type (sample descriptor will be attached)
2. Create 200+ pages with the create content create API that include labels
3. Send content fetch API call on that custom content type, with limit=200, start=0, and expand=metadata.labels

Expected Results

All content results include label data.

Actual Results

Not all results include label data.

Workaround

One theoretical workaround is to use a lower limit value; however, this may not work consistently.