The crawl loop is kicked off before knot_edge::serve(...) is even started: call location
It is also never retried.
So behind a reverse proxy that waits for the service to be ready you end up with a chain of error 400, and no crawl ever (unless you kick it off yourself manually).
Suggested fixes: configurable delay, or retry logic? the crawl request should probably have a default delay anyway, even if not adding a configurable one.
this probably explains some things about the manual crawls we've done with people, thanks :p