High volume of 404s on GET v1.0/public/{eventIdOrSlug} (88 in 24h)

[claude]

What was found

88 requests to GET v1.0/public/{eventIdOrSlug} returned 404 Not Found in the last 24 hours. This is the public-facing event lookup endpoint.

Affected service

• Microsoft.Azure.WebJobs.Script (Azure Functions host)

Error details

Endpoint	Result Code	Count
GET v1.0/public/{eventIdOrSlug}	404	88

Frequency

88 occurrences in a single 24h window, making it the highest-volume request failure after TaskCanceledException exceptions.

Likely cause

• Stale links: External links or social media posts pointing to events that have since been deleted or had their slug changed
• Missing event data: Events that exist in the frontend/CMS but have not been published to the API backend
• Bot/scraper traffic: Crawlers enumerating slugs — however the volume (88) suggests real users are affected

Suggested fix

• Review which specific event slugs are being 404'd (add slug to log context or query AppRequests with url field)
• Implement a redirect strategy: if an event slug has changed, redirect old slug → new slug (301)
• Confirm that all published Sanity CMS events are correctly synced to the API
• Add a custom 404 response body for this endpoint to guide users back to the events listing page