Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase Crashlytics
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Navigate to the schedule settings view
  • Configure your release schedule
  • Viewing your release schedule

Was this helpful?

  1. Using Runway
  2. App settings

Schedule settings

PreviousNotifications settingsNextBeta testing settings

Last updated 2 months ago

Was this helpful?

Use the release schedule to set up a regular cadence (sometimes referred to as a ) and completely key events along the way like kickoff, submission, and release.

Once your release schedule is configured, Runway will automatically apply target dates to your upcoming releases according to your specified release cadence.

Navigate to the schedule settings view

  1. Select an app in the top left corner from the Switcher

  2. Navigate to App Settings by clicking the gear icon (⚙️) at the top of the Timeline sidebar

  3. Click on Schedule in the sidebar

Configure your release schedule

1. Specify how often you'll be releasing updates to this app

  • Weekly (or more) - Releasing one or more releases every week

  • Bi-weekly - Releasing every two weeks

  • Monthly - Releasing once a month

  • Not enabled - Release schedule is OFF: Runway will not create target dates

Some configurations of the kickoff, submit or release will only trigger if target dates have been set. If your release schedule is disabled, you will need to set target dates manually on each release in order for these automations to run.

2. Choose the day of the week, time, and time zone for release kickoff, submission, and release dates

Configure a weekday, time, and timezone for at least one of target kickoff, submission or release (Apple platforms only). For the Weekly (or more) option, you can also optionally add multiple sets of dates to configure a schedule that involves shipping multiple releases within a week. For example, the following configuration is valid for teams looking to ship two releases in a week:

First release:

  • Kickoff Mondays at 9am

  • Submit Wednesdays at 2pm

  • Release Fridays at 9am

Second release:

  • Kickoff Tuesdays at 9am

  • Submit Fridays at 12pm

  • Release Mondays at 9am

Currently, the maximum amount of time supported between release events is one week.

For example, if you want to kick off your releases on Mondays, at 12:00pm, the latest you can configure your submission day & time for is the following Monday, at 11:00am.

3. Save your changes

Target dates will be applied to any current and upcoming releases active in Runway, unless target dates have previously been set.

If you've configured your schedule with the Weekly (one or more) option, Runway will apply target dates to the first N upcoming releases, where N is the number of release date sets you've configured for your cadence. For example, if you've configured your cadence to ship three releases within a week, then target dates will be automatically applied to the first three active releases in Runway.

Runway will not recalculate target dates for releases that already have target dates set.

Runway will not apply target dates to releases that are marked as hotfixes.

Viewing your release schedule

To view the release schedule for all releases for a given app in Runway, visit the "Release schedule" page accessible from the main App overview page navigation bar.

The release schedule is accessible on the "Release schedule" page on any release, and at the app level. From here you can view key dates for a given release, including kickoff, submission and (if applicable) release. You can also update target dates and pause your schedule cadence. For more details visit the .

🎛️
Release schedule documentation
release train
automate
App release schedule
release cycle automations