Hi Support Team,
I have noticed an issue where a feature that has been deleted is still being referenced in our download logs. Specifically, the feature homepage-accounting-service appears in the Usage-2024-11-21.csv file, even though it has been removed from our system.
This issue raises a few concerns:
- Why is the deleted feature still being logged?
- Is this causing unnecessary API calls?
- How can we resolve this issue to ensure that deleted features are no longer referenced in our logs?
Your assistance in resolving this matter would be greatly appreciated.
Thank you,
Hi,
what is a deleted feature?
The log only logs request. If you have references somewhere in your code to this item, it is still queried and would still cause API calls.
Hi,
By “deleted feature,” I mean a line of code and schemas that have been removed from our codebase. Despite this, the feature is still being queried approximately 12,300 times, resulting in a 404 status. Normally, it should be completely removed and not cause any API calls.
Can you help me understand why this is happening and how we can resolve it to prevent unnecessary API calls?
I am not so sure how to help here.
Lets say you create a content item that you query by slug, something like $filter=data/slug/iv eq my-article` and then “my-article” is super popular and is shared and people use links. Of course you would still have a lot of queries for this article, even though you delete it on Squidex.
The only solution is to blacklist the article on your frontend to avoid any calls to it. But it really depends on your structure and your code and hundreds of details. You have to figure this out yourself.