Dear Jradah Anis,
Please understand that this forum is a public platform, and moderators will modify your question to cover your personal information in the description. Please notice to hide these personal or organization information next time you post error or some information to protect personal data.
This pattern is more consistent with a recent SharePoint Online client-side deployment or regression than with a site-specific configuration issue. At present, I am not aware of any publicly documented service advisory for this exact behavior, so I recommend checking Service Health and opening a Microsoft Support case if the impact is ongoing.
Please check your Microsoft 365 Service Health dashboard for any active SharePoint Online incidents or advisories:
In the Microsoft 365 Admin Center, navigate to Health > Service health and review any active SharePoint Online events.
For more detailed information How to check Microsoft 365 service health
And if no related advisory is listed and the issue continues across multiple sites, I would recommend opening a Microsoft support ticket so the product team can investigate whether this is related to a recent service deployment.
You can contact them via submit support ticket in Microsoft 365 Admin Center > support > help & support.
Or you can call them via phone service number: Customer service phone numbers - Microsoft Support
Please understand that as a forum user, I do not have access to your tenant, backend diagnostics, or Microsoft's internal incident records.
Feel free to reach out if you have any other questions.
Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.