[J4] News Items in Category view not visible (items created with FC v4.1.1 and FC 4.0.x), Fixed in v4.1.3

I have a problem with the category view. When an article is newly entered, it does not appear in the category view (e.g. template category view grid). The article has the status Published. If I open the article with the Joomla Com_Content component and save it again, the article is displayed. The problem appeared only after the update to version 4.1.3.

Joomla 4.2.3
Flexicontent: 4.1.3
PHP: 8.08

hello maybe its publish down problem
can you update flexicontent with last dev version
github.com/FLEXIcontent/flexicontent-cck...efs/heads/master.zip

i test it with your dev version. The same problem. The item appears in the frontend only after it has been saved with com_content.

hello to be more precise article is create via joomla fform or flexicontent form ?
we publishg some new update this morning can you do a new update via same link ?

Hello,

i create the article via flexicontent form in the backend.
I will test it with your new update.

I have installed and tested the version from the link above.
Created a new article with Flexicontent. (see screenshot) It is published and is not displayed in the frontend. If I open and save the same article with the Joomla form, the article appears in the frontend.
I still have PHP 7.4 running on the site, because there are but have also tested it with PHP 8.0.8.

hello can you send me an access ?

Yes i will send you a private message.

hello i update to last dev version after
- 1 create 'test com3elles'
- go to aktuelles ..
- go to rathausnews
=> it display no problem
can you retest it and validate ?
regards

I have now tested it again.
- Article re-entered and published.  -- Test 3
- The article is visible in the front end in the item view, but not in the category view.
- After a certain time I can not say the exact time window, appears in the dashboard „update temporary item data“
- After the update, the item appears in the category also in the frontend.
Is it possibly due to some cache? See screenshots.