a month ago
Your deployment for scraper-worker in dsrecruit-web-backend crashed within the production environment.
Pinned Solution
a month ago
I’d check your application logs for more information about the crash. I’d also make sure to handle errors in your code if your scraper encounters a failed request.
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
I’d check your application logs for more information about the crash. I’d also make sure to handle errors in your code if your scraper encounters a failed request.
19 days ago
Hey
The email you’re getting just means the process inside the scraper-worker container exited with a non-zero code (crashed). Railway sends that notification automatically whenever a deployment crashes.
The most useful next step is to look at the Deploy Logs of the crashed deployment (not the build logs). Usually you’ll see one of these:
- The scraper hit a network timeout / connection refused while trying to reach a website
- An unhandled exception (missing selector, rate limit, blocked by the target site, etc.)
- The process ran out of memory
- A dependency failed to load at runtime
Quick things to check:
- Open the failed deployment → Deploy Logs and look at the last 20–30 lines. That’s where the real error almost always is.
- Make sure your scraper code catches exceptions properly (especially network errors and HTTP 4xx/5xx). Right now if any request fails hard, the whole process dies and Railway marks it as crashed.
- If the scraper is long-running, consider adding a small health check or a simple restart loop so a single failed job doesn’t kill the whole service.
- Check memory usage in the Metrics tab — scrapers that load a lot of pages or use Puppeteer/Playwright can easily OOM on the default resources.
If you can paste the last part of the Deploy Logs from one of the crashes, I can tell you exactly what’s killing it.
Also worth checking whether the target websites started blocking the Railway IP range recently — that happens quite often with scrapers.
Let me know what the logs show
Status changed to Solved 0x5b62656e5d • 18 days ago