Updated page 404?

[stephenmeehanuk]

Hi

Has anyone come across this before?

A working entry 404s after it's edited? This only happens on a single entry. All the other entries are working.

When saving the entry I can see the static cache is cleared

  2025-05-08 04:51:56 Statamic\Git\CommitJob ......................... RUNNING
  2025-05-08 04:51:55 Statamic\StaticCaching\Invalidate .............. RUNNING
  2025-05-08 04:51:55 Statamic\Search\UpdateItemIndexes ......... 41.72ms DONE
  2025-05-08 04:51:55 Statamic\Search\UpdateItemIndexes .............. RUNNING
  2025-05-08 04:51:46 Statamic\Git\CommitJob ................... 967.21ms DONE
  2025-05-08 04:51:45 Statamic\Git\CommitJob ......................... RUNNING
  2025-05-08 04:51:05 Statamic\Jobs\HandleEntrySchedule .......... 9.23ms DONE
  2025-05-08 04:51:05 Statamic\Jobs\HandleEntrySchedule .............. RUNNING

But the page continues to 404?

I've tried clearing the cache for the whole site at /cp/utilities/cache but that doesn't fix it either.

I've pulled a copy of the site locally and the URL doesn't 404.

Git is up to date, so I know the queue is working.

git status
On branch main
Your branch is up to date with 'origin/main'.

Environment
Application Name: Website
Laravel Version: 11.44.2
PHP Version: 8.3.13
Composer Version: 2.8.8
Environment: production
Debug Mode: OFF
URL: website.com
Maintenance Mode: OFF
Timezone: America/New_York
Locale: en

Cache
Config: CACHED
Events: NOT CACHED
Routes: CACHED
Views: CACHED

Drivers
Broadcasting: pusher
Cache: file
Database: sqlite
Logs: stack / single
Mail: smtp
Queue: redis
Session: redis

Livewire
Livewire: v3.6.2

Statamic
Addons: 6
Sites: 1
Stache Watcher: Disabled
Static Caching: half
Version: 5.52.0 PRO

Statamic Addons
jonassiewertsen/statamic-jobs: 1.5.0
jonassiewertsen/statamic-live-search: 2.2.0
marcorieser/statamic-livewire: 3.9.0
statamic/collaboration: 1.0.0
statamic/importer: 1.8.1
visuellverstehen/statamic-anchor-navigation: 1.0.0

[stephenmeehanuk]

Changing the URL loads the page. I added a -1 to the end. But if I revert to the original URL it 404s again.

If I add ?_=123456789 to the end of the URL, it works.

So it must be related to caching... I'll keep digging.

[stephenmeehanuk]

Running php artisan route:clear didn't fix it, but php artisan optimize:clear did. It's good it's working, but it's odd this was even an issue.

Has anyone else come across this? My client shouldn't need support with something like this.