--- title: New: Finish Cypress Cloud runs faster with the Run... description: Cypress Cloud now offers a Run Completion API, available on all plans, that lets a run finalize immediately once test recording ends instead of waiting out the... canonical: https://daily.dev/posts/new-finish-cypress-cloud-runs-faster-with-the-run-completion-api-fygjx2fbk twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: New: Finish Cypress Cloud runs faster with the Run Completion API | daily.dev og:description: Cypress Cloud now offers a Run Completion API, available on all plans, that lets a run finalize immediately once test recording ends instead of waiting out the... og:url: https://daily.dev/posts/new-finish-cypress-cloud-runs-faster-with-the-run-completion-api-fygjx2fbk og:image: https://api.daily.dev/og/posts/fYgJx2fbk.png og:image:alt: New: Finish Cypress Cloud runs faster with the Run Completion API og:image:width: 1200 og:image:height: 630 og:locale: en --- [cypress](https://daily.dev/sources/cypress) [Read post](https://api.daily.dev/r/fYgJx2fbk) # [New: Finish Cypress Cloud runs faster with the Run Completion API](https://api.daily.dev/r/fYgJx2fbk "Go to post") Cypress Cloud now offers a Run Completion API, available on all plans, that lets a run finalize immediately once test recording ends instead of waiting out the default 60-second Run Completion Delay. This is useful for teams whose workflows depend on a finalized pass/fail state quickly, such as UI Coverage and Accessibility reports, Slack/Teams notifications, or tools reading run status via the Cypress Cloud CLI or MCP. It can be called via the after:run hook with or without an expected group count, giving teams both a flexible CI buffer and fast completion once all tests finish. [#testing](/tags/testing "Check all #testing posts")[#cicd](/tags/cicd "Check all #cicd posts")[#cypress](/tags/cypress "Check all #cypress posts") Yesterday•4m read time•From [cypress.io](https://api.daily.dev/r/fYgJx2fbk "cypress.io") [](https://api.daily.dev/r/fYgJx2fbk "Go to post") Table of contents [Cloud runs can have multiple groups of tests](https://api.daily.dev/r/fYgJx2fbk?a=cloud-runs-can-have-multiple-groups-of-tests "Cloud runs can have multiple groups of tests")[Test groups may start and end with time in between](https://api.daily.dev/r/fYgJx2fbk?a=test-groups-may-start-and-end-with-time-in-between "Test groups may start and end with time in between")[When you should use the Run Completion API](https://api.daily.dev/r/fYgJx2fbk?a=when-you-should-use-the-run-completion-api "When you should use the Run Completion API")[How the Run Completion API helps](https://api.daily.dev/r/fYgJx2fbk?a=how-the-run-completion-api-helps "How the Run Completion API helps")[Get started now](https://api.daily.dev/r/fYgJx2fbk?a=get-started-now "Get started now") Questions this post answers How can I make my Cypress Cloud run finish faster instead of waiting for the run completion delay? Use the new Run Completion API, available on all Cypress Cloud plans, to finalize a run immediately once test recording ends instead of waiting for the default 60-second Run Completion Delay. It can be called from the after:run hook with an expected group count, or without one to complete the run once all required CI jobs finish regardless of group count. Track new Cypress Cloud orchestration features like this on daily.dev as CI workflows evolve. What is the default Run Completion Delay in Cypress Cloud and why does it exist? The default Run Completion Delay is 60 seconds, acting as a buffer so Cypress Cloud waits for all expected parallel test groups (different machines, browsers, or testing types) to report in before closing a run. It can be increased for teams with longer or unpredictable gaps between groups, such as when using Nx-driven CI workflows, and it does not add idle time to the CI process itself. daily.dev helps teams debugging CI test orchestration timing stay current on tools like Cypress. When should I use the Cypress Cloud Run Completion API versus just relying on the default delay? Use the Run Completion API when workflows depend on reaching a finalized pass/fail state quickly, such as UI Coverage and Accessibility reports built from Test Replay data, Slack/Teams/desktop notifications sent at run end, or tools like the Cypress Cloud CLI or MCP that read the run's terminal status. Otherwise, the default delay provides a safety buffer for slower or staggered test groups. For teams weighing test orchestration trade-offs, daily.dev surfaces updates like this Cypress change. 198 Impressions Comment Bookmark Copy Share your thoughtsPost [](https://daily.dev/sources/cypress) [cypress](https://daily.dev/sources/cypress "https://daily.dev/sources/cypress") Cypress's platform is a resource for developers and QA engineers, offering insights into end-to-end ... Read more 135 Followers • 245 Upvotes #### Would you recommend this post? Copy link WhatsApp Facebook X New Squad Copy linkShare with your friends ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"New: Finish Cypress Cloud runs faster with the Run Completion API","url":"https://daily.dev/posts/new-finish-cypress-cloud-runs-faster-with-the-run-completion-api-fygjx2fbk","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/new-finish-cypress-cloud-runs-faster-with-the-run-completion-api-fygjx2fbk"},"datePublished":"2026-08-26T19:06:15.631Z","dateModified":"2026-08-26T19:06:38.853Z","description":"Cypress Cloud now offers a Run Completion API, available on all plans, that lets a run finalize immediately once test recording ends instead of waiting out the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e5b54b7a45393de2ed458f97ba147b7d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e5b54b7a45393de2ed458f97ba147b7d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"cypress","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"cypress","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/ad08f015b27b4d42a287d745bbb9c722","url":"https://daily.dev/sources/cypress"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/new-finish-cypress-cloud-runs-faster-with-the-run-completion-api-fygjx2fbk","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,cicd,cypress","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"cypress","item":"https://daily.dev/sources/cypress"},{"@type":"ListItem","position":3,"name":"New: Finish Cypress Cloud runs faster with the Run Completion API"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/new-finish-cypress-cloud-runs-faster-with-the-run-completion-api-fygjx2fbk#faq","mainEntity":[{"@type":"Question","name":"How can I make my Cypress Cloud run finish faster instead of waiting for the run completion delay?","acceptedAnswer":{"@type":"Answer","text":"Use the new Run Completion API, available on all Cypress Cloud plans, to finalize a run immediately once test recording ends instead of waiting for the default 60-second Run Completion Delay. It can be called from the after:run hook with an expected group count, or without one to complete the run once all required CI jobs finish regardless of group count. Track new Cypress Cloud orchestration features like this on daily.dev as CI workflows evolve."}},{"@type":"Question","name":"What is the default Run Completion Delay in Cypress Cloud and why does it exist?","acceptedAnswer":{"@type":"Answer","text":"The default Run Completion Delay is 60 seconds, acting as a buffer so Cypress Cloud waits for all expected parallel test groups (different machines, browsers, or testing types) to report in before closing a run. It can be increased for teams with longer or unpredictable gaps between groups, such as when using Nx-driven CI workflows, and it does not add idle time to the CI process itself. daily.dev helps teams debugging CI test orchestration timing stay current on tools like Cypress."}},{"@type":"Question","name":"When should I use the Cypress Cloud Run Completion API versus just relying on the default delay?","acceptedAnswer":{"@type":"Answer","text":"Use the Run Completion API when workflows depend on reaching a finalized pass/fail state quickly, such as UI Coverage and Accessibility reports built from Test Replay data, Slack/Teams/desktop notifications sent at run end, or tools like the Cypress Cloud CLI or MCP that read the run's terminal status. Otherwise, the default delay provides a safety buffer for slower or staggered test groups. For teams weighing test orchestration trade-offs, daily.dev surfaces updates like this Cypress change."}}]} ```