Release · S362-S362
Pages answer straight away, even after a quiet spell
On 11 October the company that runs our servers stopped more than a hundred requests for VEILOS pages before VEILOS could answer them, and showed its own error message instead. Most of those were a monitor that checks the home page every five minutes; for about nine hours that day it was told the site was down. Our own health checks all read normal the whole time, because a request that is stopped that early never reaches them. The cause: VEILOS keeps a ready copy of each public page for one minute. Anyone arriving later than that waited while the page was rebuilt from the whole record, and on our free hosting plan that rebuild takes more computing time than a single request is allowed. Now, if the ready copy is up to fifteen minutes older than that, you are given it at once and a new copy is built behind you for the next reader. If you are signed in, or you have chosen a theme, nothing changes: you always get the page built for you at that moment. A page nobody has opened for more than sixteen minutes is still rebuilt while you wait, so this makes the failure rarer; it does not remove it. Removing it needs either the paid hosting plan or a change to how the record is stored, and both are decisions for the founder. We also added a check that asks the hosting company directly how many requests it stopped, and it runs after every release.