504 Gateway timeout error



  • Official comment
    Jillian Lohndorf

    Hi Andra,

    Our engineers have pushed a fix for this issue. It turns out that 80% of the site's content was coming from a single line of JavaScript, and the time it took to load was longer than our default replay settings. We have increased the default loading time from 30 seconds to 2 minutes, which should reduce the likelihood of this occurring. If you save this crawl, you should see the fix apply to other crawls of this seed as well.

    If you see this error message in the future, whether it’s on a seed, a sub-page, or throughout an entire site, it’s worthwhile checking in with us so we can investigate the cause and its resolution.


    Comment actions Permalink
  • Avatar
    Andra Kidwell

    Hi Jillian,

    Thank you for your quick work! That seems odd to place that much on one line of JS. I’m glad the engineers were able to figure something out for us. I’ll save the test crawl and let you know how it goes.


    Comment actions Permalink

Please sign in to leave a comment.