[BUG] cache invalidation / jobs showing as "no longer available"

[gedw99]

“ This job posting is no longer available“ is caused by the db being out of sync with the server side html cache ?

Or is it client side not invalidating the cache when the server cache changes ?

[ghost]

I am not sure if you refer to a bug - job visible on landing page but doesn't work when clicking on it? - OR - just simply that expired jobs show an ugly 404. Can you please help elaborate on what the issue is and how to reproduce? If it's a bug I might allocate some budget for it

[gedw99]

It’s definitely the former .

not a 404.

Personally I think we can do better than showing stake data . I have not dig into the caching layer server side yet which my hunch is where the problem is.

This reminds me of CQRS domain with read only side getting stale. We could push an event on d change to force specific cache of that psge to be evicted.

just an idea

[ghost]

thank you @gedw99 can you please help out and explain steps on how to reproduce it, I will open a bounty if i can reproduce it so you can fix it up