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

Avatar

Avatar

SebNamek

Avatar

SebNamek

SebNamek

03-11-2020

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?

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar

kiranparab

Avatar

kiranparab

kiranparab

03-11-2020

Avatar

Avatar

kiranparab

Avatar

kiranparab

kiranparab

03-11-2020

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.

 

Hi Kiranparab,

I dug a bit deeper and one of my pages has a parallel page that is published and the other isn't (ex offers > all-offers, featured-offers) all-offers is working and featured isn't.

Based on your feedback:

1. What is the author outbox and how can I validate that?
2. I don't think this is the issue we tried flushing cache and still no luck.
3. How would I know if the publisher is faulty? Isn't there only one publisher and if it's faulty how can I fix it?


1. What is the author outbox and how can I validate that?

-> You can validate if there is any issue in activation of the page

-> You can validate the outbox of your replication agent on Author

 

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

-> You can login to Publisher and see if the page exist on each publisher

 

 

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 !

Thanks for confirmation. Try to see if you can handle the SSR validation usecase in sightly tag to smooth replication of the pages