On long graphql requests in Genegraph, consider a server timeout and message to client indicating server slowness

[toneillbroad]

Would need to determine the proper wait period. Timeout message would go in the error bag.

[larrybabb]

@toneillbroad could you add a little more background to this so we know when/who/where it originated (it's fine if it's from you). Also whether this is something that links back to a stakeholder concern or direct request - that would be very helpful to know.

If you know could you also provide,

• a notion of priority or ugency
• whether this was an assignment for you or someone else
• what individual can I go back to to get more requirements

[toneillbroad]

This was spoken about in the postmortem when Google Kubernetes recycles our Genegraph servers during the day. Rather than having portions of the website unavailable if there is an application or server failure, we spoke of having a request timeout that returns a "server is currently experiencing delays" rather than a spinning "loading" message. The stake holders were us developers. Priority: Nice to have Assign to: There is client side, and server side tasks associated with this (Tristan or I could handle server side I suspect) Individual to go back to to get more requirements: Scott, Phil, Tristan and Terry