DeviceCloud
Console UIMaestro DocsDiscord
  • Welcome to DeviceCloud
  • Getting Started
    • Quick Start
    • API Keys
    • Executing Flows
    • Limits
    • Upgrade Guide
    • Device Configuration
  • CI/CD Integration
    • Overview
    • GitHub Actions
    • BitRise
    • Any CI
    • Status API
  • Reference
    • Test Execution
    • App Management
    • Environment Variables
    • Device Orientation
    • Device Locale
    • Async Execution
    • Retry Strategies
    • Report Formats
    • Download Artifacts
    • Quiet Mode
    • Maestro Versions
    • Test Run Name
    • Google Play APIs
    • Email Notifications
    • Exit Codes
    • Runner Type
  • Infrastructure & Security
    • IP Addresses
    • Security Overview
    • IT Security Policies
    • Enterprise SSO
  • Legal
    • Service Level Agreements
    • Open Source Notices
    • Privacy Policy
    • Terms and Conditions
    • Refund Policy
Powered by GitBook
On this page
  • Basic Usage
  • Setting Retry Count
  • Understanding Retries
  • What Gets Retried
  • What Doesn't Get Retried
  • Cost Implications

Was this helpful?

Edit on GitHub
  1. Reference

Retry Strategies

Device Cloud provides retry functionality to handle flaky tests and temporary failures.

Basic Usage

Setting Retry Count

dcd cloud ... --retry 3

This will:

  • Run the test initially

  • Retry up to 3 times on failure

  • Stop on first success

  • Report final status

Understanding Retries

What Gets Retried

  • Failed test executions

  • Infrastructure issues

  • Device availability problems

What Doesn't Get Retried

  • Invalid flow files

  • Missing dependencies

  • Authentication failures

Cost Implications

Note: Each retry counts as a separate test execution and will deduct credits from your account.

PreviousAsync ExecutionNextReport Formats

Last updated 4 months ago

Was this helpful?