Is railway limiting my console.logs?
I've noticed that if I have too many console.logs, railway just seems to drop them. Can anyone explain what is going on here? I had a forloop performing a few hundred operations, and I was just completely losing the logs letting me know when the entire loop had completed. Thank you.
Solution:Jump to solution
railway does indeed have a throttle on how many logs /second they will ingest, how fast do you think you're printing your logs?
5 Replies
Project ID:
610ccb09-e540-4b0a-8ee2-3dd2e5d3b435610ccb09-e540-4b0a-8ee2-3dd2e5d3b435?id=96a48edd-d90b-4d05-b178-864793fd7704
Solution
railway does indeed have a throttle on how many logs /second they will ingest, how fast do you think you're printing your logs?
They were pretty quick. I understand that, I just wish it would have let me know. Spent a few hours trying to debug. The loop had 200 iterations, and each iteration had 6 console.logs
that wouldn’t definitely cause log lines to be discarded