Hey there! We've found the following might help you get unblocked faster:

• 🧵 413 Request Entity Too Large

If you find the answer from one of these, please let us know by solving the thread!

getting the same issue with same error. terrible timing

just got a successful build. 480 seconds

ERROR: failed to build: failed to solve: failed to push production-us-east4-eqdc4a.railway-registry.com/: unknown: blob upload unknown to registry

Finally deployed after 14 minutes

I am OP. Successfuly deploying now, as well.

Hey Clayton and 7fromheaven, ack on the impact for build times. I however don't see a project id linked, can you provide one for me so that I can give that information to the engineering team for an investigation?

Hi - i was running perfectly yesterday and am having the same issue. Over an hour and no logs after deploy. Us-east-4. My build is over an hour old and no logs, no deploys. Proj ID: 032da120-6679-4e48-b2b2-57a6f9d9e782

Here's another one. 032da120-6679-4e48-b2b2-57a6f9d9e782.

Okay - i have an update.

I had all my runners set to run on a cron Schedule. Logs showed only for the cron runs and I could NOT invoke cron runs early. I removed the cron for one of my runners, logs came back and the other runners crashed too.

Scary thing when its green deploy but no logs and no function

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Ack, running an investigation into the reliability of the cron behavior. Sorry for the late reply, needed to add some instrumentation to see where the problem was. After we got a few more reports, we know it's on our side to fix. Will give you updates as we go along.

Hello,

An update: We have made several changes to our CRON scheduling system, and from our internal metrics, we have seen this make a massive improvement in CRON execution delay and have eliminated missed CRONs. Additionally, the Run Now button starts the job much faster.

But please let us know if this isn't the case for you!

Best,
Brody

🛠️ The ticket Scheduling Inaccuracy Issue has been marked as in progress.

✅ The ticket Scheduling Inaccuracy Issue has been marked as completed.