Author: Jonathan Rivera
Updated: August 2024
Audience: Everyone
Environmental details: Self-hosted and Cloud-hosted
Summary
The globalSortOrder for items is -1 when retrieving items via the API.
For example,
f
Solution
This is working as expected. The moves are usually complete, but when there are a lot of moves, it may take longer for that field to update.
- Wait for the globalSortOrder to update
- Run a project cleanup if needed
Cause:
The global sort order of -1 is expected. This is temporarily set to -1 for items sorted while the document node sort job runs. Suppose a lot of work is being done rapidly via the API, such as creating, deleting, or moving items. In that case, you will occasionally see this value if you immediately try to read the global sort order. The sort job runs every minute.
Prevention:
This field is a database reference field and is not meant to be used in this manner.
Additional Information/Metadata:
- API
- Batch move
- Batch deletion
Feedback: Please leave feedback in the comments below.
Related to
Comments
0 comments
Please sign in to leave a comment.