Skip to main content
All CollectionsTest
[Migrated] Test or Test Run timed out
[Migrated] Test or Test Run timed out

Diagnosing timeouts in App Center Test

Jihye E avatar
Written by Jihye E
Updated over 4 years ago

The latest version of this guide is here: https://docs.microsoft.com/appcenter/test-cloud/troubleshooting/time-outs

Overview

Time out errors occur when individual tests, or a test run on a device exceeds execution time-limits in App Center. These limits are as follows:

  • Individual test time limit - execution time of 30 minutes.

  • Total execution time limit per device - 6 hours if you have a paid Test license; otherwise the limit is 1.5 hours. 

Note that these limits only apply to the actual execution time, including time spent installing your app & running your tests. Time that a device is queued for running or processing completed test results do not count against these limits.
​

Diagnosing timeouts

Identifying timeouts

  • If an Individual test times out; the last test step for the affected device will generally have an error message indicating the 30 minute limit in milliseconds:
    ​test exceeded 1800000ms 

  • If the Total execution time limit for a device is reached, test results for that device will not be displayed. 

Information to compare

  1. How long does the timed out test or test suite take to run locally on a similar device & OS version?
    - Emulators & simulators are not as accurate for this comparison since App Center Test only uses real devices.
    - Tests may need additional time to run in App Center compared to locally due to time spent taking screenshots or connecting to & communicating with servers.
    ​

  2. If the individual test or test suite completes successfully sometimes but not always; you can check the Duration of tests or devices. If it's close to the timeout limits then small variances in execution time could make the difference between completion vs. timing out. (Note: The Duration of the entire test run is not relevant, because that is the combined duration of all devices in the test, even those which did not time out.)
    ​

  3. If you're unsure which devices may have hit the total execution time limit, you can reach out to App Center Support with a link to the test run and they should be able to determine this by looking at backend data for the run. 

Did this answer your question?