Job fails with 'Failed: timeout' but was only loading for 30 minutes
cc @DioneMentis please add further detail to this issue if needed.
Expected behaviour
Jobs don't fail due to timeout so quickly (we expect them to fail due to timeout only after 4 hours).
Current behaviour
Some jobs get a 'Failed: timeout' error even when they have only loaded for 30 minutes.
Steps to reproduce
Example that I encountered is here and screenshot below.
Environment
Chrome on Mac Sierra OS.
Possible solution
[Not required. Suggest a fix for the bug]
NCBI's priority feedback
[Select "Y" or "N" and provide an explanation]
- This bug is blocking NCBI's work on migration planning for deployment 1 (Y/N)
- This can be prioritised after deployment 1 (Y/N)
QA Steps
[To be completed by Coko once dev is done]