Retry Failures While Run in Progress

RWX has the best developer experience of any CI/CD platform for retrying failures. Unlike GitHub Actions, tasks that fail on RWX can be retried immediately, even while other tasks are still running.

Additionally, RWX executes at a more granular level than any other CI/CD platform. Tasks on RWX are equivalent to steps on other platforms.

On other platforms, if the third step in a job fails, the first two steps have to be re-executed. On RWX, each step is represented as an individual task, and the third step (for example) can be retried without having to re-execute the first two.

#GitHub Actions Requires Canceling to Retry

GitHub Actions has the worst retry experience of any CI/CD platform. If one job fails, other running jobs have to be canceled to retry the job that failed.

The "re-run" button does not show up until clicking "cancel workflow." It's a shockingly bad limitation.

When a job fails, engineers have to decide if they want to stop everything to retry right away, or wait for the other jobs to finish before retrying the failure.

#GitHub Actions Demo

#RWX Demo

#Code

#GitHub Actions

on:
  push:

jobs:
  will-succeed:
    runs-on: ubuntu-24.04
    steps:
      - run: sleep 15

  fails-fast:
    runs-on: ubuntu-24.04
    steps:
      - run: exit 1

#RWX

The RWX demo uses a clever trick to get the task to succeed on retry.

base:
  os: ubuntu 24.04
  tag: 1.1

tasks:
  - key: task-one
    run: sleep 15
    cache: false

  - key: task-two
    run: |
      if [ "$ATTEMPT_NUMBER" = "1" ]; then
        exit 1
      fi
    env:
      ATTEMPT_NUMBER: ${{ task.attempt-number }}