Scrapers sometimes error before they run (during the compile?). When this happens you get told that there's an error, and what the error code is, e.g. "Last run failed 22 minutes ago with status code 128." I've seen status codes 128 and 255. There's no clue to the person what has gone wrong or what they can do about it.
A number of people have reported these errors, and being confused by the status code. See
As far as I know status code 255 only happens on a failed compile or when you try to stop a scraper and the container has disappeared so we definitely shouldn't be seeing this.
Firstly, we should fix whatever is causing these errors, so people’s scrapers just run.
If the root cause of the errors is here to stay:
are these status codes actually useful to people? If they don't help people do what they want, should we remove them all together?
if the information is useful, how might we make them less cryptic so people don't need to ask what they mean? Could we replace the code with a description of the error status, e.g. "your scraper exceeded our memory limit"?
I don't know what the solution is, but these codes seem to be confusing/frustrating people (including me) in there current incarnation.
Scrapers sometimes error before they run (during the compile?). When this happens you get told that there's an error, and what the error code is, e.g. "Last run failed 22 minutes ago with status code 128." I've seen status codes 128 and 255. There's no clue to the person what has gone wrong or what they can do about it.
A number of people have reported these errors, and being confused by the status code. See
https://github.com/openaustralia/morph/issues/1086 :
https://github.com/openaustralia/morph/issues/422 :
https://help.morph.io/t/scrapers-failing-with-status-code-128-and-255/314/3
@henare seems to know what status code 255 is:
Firstly, we should fix whatever is causing these errors, so people’s scrapers just run.
If the root cause of the errors is here to stay:
I don't know what the solution is, but these codes seem to be confusing/frustrating people (including me) in there current incarnation.