Timed out waiting for asynchronous Angular tasks to finish: Protractor synchronization issue

Issue Overview

The error Timed out waiting for asynchronous Angular tasks to finish surfaces intermittently in Protractor tests when the Angular zone’s task queue never drains within the default allScriptsTimeout (11 s). This timeout is triggered by the global waitForAngularEnabled flag, which forces Protractor to poll window.getAllAngularTestabilities() until the queue is empty.

Goal & Constraints

We need a reliable way to diagnose and mitigate these timeouts in hybrid applications that mix Angular routes with non‑Angular pages or third‑party widgets that keep macro‑tasks alive. The current design forces the flag to be toggled globally, leaking state across parallel specs and making it difficult to isolate failures to a single page or frame.

Unresolved Decision

The Protractor team has not provided a scoped synchronization mechanism, leaving teams to toggle waitForAngularEnabled per spec or manually reset it after each test. This global approach is a known source of flakiness in parallel execution environments.

Specific Questions

• Is there a supported method to scope waitForAngularEnabled to a particular page, frame, or component rather than globally?
• What are the implications of disabling waitForAngularEnabled on parallel test runs, especially regarding test isolation and state leakage?
• Can configuration options or custom Protractor extensions mitigate false‑positive timeouts caused by persistent third‑party macro‑tasks?