Deployment fails due to flaky log pulling
ivan-robert
PROOP

18 days ago

Our github actions pipeline fails around 1/3 times with error Failed to stream build logs: Failed to retrieve build log. Starting it again sometimes works.

It is a multi-step deployment with data pipelines that depend on the service being deployed. Therefore using --detach is not an option (plus we like to keep monitoring the status directly in the pipeline). I still gave the possibility to detach manually, but it is more an ugly quickfix than what we want.

CLI version 4.42.1

Code :

(...)
    steps:
      - name: Checkout code
        uses: actions/checkout@v6
        with:
          ref: ${{ inputs.checkout_ref }}

      - name: Install Railway CLI
        run: npm install -g @railway/cli@4.42.1

      - name: Deploy async worker
        env:
          RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
        run: railway up --service ${{ secrets.RAILWAY_APP_ASYNC_WORKER_SERVICE_ID }} --detach

      - name: Deploy web
        env:
          RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
        run: railway up --service ${{ secrets.RAILWAY_APP_SERVICE_ID }} ${{ inputs.attach_logs == false && '--detach' || '' }}

(...)
Solved

1 Replies

Status changed to Awaiting Railway Response Railway 18 days ago


15 days ago

We're aware of this and we'll be working to improve the CLI experience here. No firm ETA though.


Status changed to Awaiting User Response Railway 15 days ago


Railway
BOT

8 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 8 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...