Why would a published page give a 504 after a deployment that didn't affect that page

Forum|Forum|5 years ago
November 3, 2020
2 replies
3324 views

I made a change to our offers page and deployed that, after that was done our help page is now throwing a 504.

I looked into the error logs and haven't seen anything. The author instance works fine. I tried republishing and that doesn't work either.

Just seems as if the data won't make it to the publish instance. Why did this happen and how can I fix it?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by kiranparab

Is this page really published to your publishers ? Please validate parallel pages too if it respond correctly

Issues like -

1. Publishing not happened to all publishers through your replication agents. Validate the Outbox for Author instance.

2. Cached the page on dispatcher level which didnot remove the cache after activation

3. One of the publisher faulty to responed with 504 for Timeout error code.

K

kiranparabAccepted solution

Level 3

Is this page really published to your publishers ? Please validate parallel pages too if it respond correctly

Issues like -

1. Publishing not happened to all publishers through your replication agents. Validate the Outbox for Author instance.

2. Cached the page on dispatcher level which didnot remove the cache after activation

3. One of the publisher faulty to responed with 504 for Timeout error code.

S

SebNamekAuthor

Level 2

Turns out this was related to an SSR issue.

Both of these pages were using SSR without my knowledge and were changed between deployments.

In addition to this we weren't able to replicate locally because our local pages are not using SSR.

Strange that it was throwing a 504 instead of an actual error but that's something to dig into further.

Thanks for your help @kiranparab !