App.co not loading

[pstan26]

Describe the bug
tried to got to app.co and it loads a mostly blank screen.

To Reproduce
Steps to reproduce the behavior:

1. Go to app.cp
2. See error

Desktop (please complete the following information):

• Chrome
• Version 79.0.3945.130

Smartphone (please complete the following information):

• iPhone7
• Browser Chrome

[aulneau]

@wileyj says this is fixed now

[markmhendrickson]

This appears to be a recurring problem due to the site not reloading automatically after VM's reboots. I've created #785 to track its solution.

[diwakergupta]

I don't think #785 will fix this. Right now we assume app.co is a fully stateless service and if so, daily restarts shouldn't have any impact. Implementing the health-check will make the above process a bit nicer, but not much beyond that.

I suspect this is a nextjs issue and would like @hstove or @kyranjamie to spend some time confirming the root cause here.

[aulneau]

I would think this error is a caching error. Typically when there are assets that can't be found via /_next/..., it's due to a build hash not matching up with what is found locally. This could be helpful: https://github.com/nexdrew/next-build-id

[wileyj]

@aulneau in this case though, that would require the site to be running multiple builds, which currently is not the case. Sticky sessions are also enabled at the load balancer, so a request wouldn't be bouncing between different instances of the running site.
is there a way to check this build hash from the host?

[kyranjamie]

I've made PRs addressing #785 and #788. Need @hstove / @aulneau's input on whether we need to tackle #786, or whether we can find another solution, as I believe it'd require some serious refactoring.

[hstove]

Honestly, I think the best approach here is to finalize the migration to webflow. Refactoring to reduce page load size would take at least the same amount of work (probably more). Moving to webflow has more potential for the future, in my opinion.

[GinaAbrams]

+1 to move it to webflow!!! 🙏