CMS item on static page disappear after update and publish request API with the filter CMS [Created Newest / to Oldest]

[Maxime_Clauzel]

Hello everyone,

This morning a customer called to inform me that some elements had disappeared from his page after taking action.

Context :

I used Webflow + Memberstack to create a personal web application for the clients of a marketing agency.

The application allows to display appointments with the information of the appointment generated for the client in question. (Surname, first name, address, email, telephone number, company, linkedin, date of appointment etc.)

My client interacts from different webflow pages to add information, appointment date and other when necessary, or from a system like Lemlist, walaxy and others…

I capture the information from a specific form depending on the information required and I modify the object using the API with UPDATE and PUBLISH requests.

Problem :
When my customer modifies an ITEM, the content is updated,
But it disappears from the static page on which it can be modified.

I changed the filter from : [Created Newest / to Oldest] → [Publish Newest / to Oldest].
And the ITEM appears correctly with the updated information.

I don’t understand why the [Created Newest / to Oldest] filter makes the ITEM disappear from the list (I couldn’t find it in the page below).

Thanks for your Help

[CloudCoder (Fiza Tabassum)]

The issue occurs because the Created Newest/Oldest filter sorts items by their creation date, which remains unchanged when an item is updated. After an API update and publish, the item’s publish date changes, but its creation date doesn’t, causing it to fall outside the filter criteria and disappear. Switching to the Published Newest/Oldest filter resolves this by sorting items based on their last publish action, ensuring updated items remain visible. If you need further help or a deeper dive into your setup, feel free to reach out—I’d be happy to assist and learn more about your project.

[Maxime_Clauzel]

Sorry for the confusion, but this concerns the [Sort Order] element and not the filters.

(Otherwise I agree with you).
If Necessary I can make a screen recording to demonstrate that this feature seems to be failing.