## TL;DR
Use the Adobe User Management API instead of the browser console. Browser SSO logins are flaky under automation; the API is the supported path.

## Error
```text
(agent timed out on the Adobe admin console SSO login; Adobe audit skipped; no error text)
```

## Steps
1. Confirm the stall is the SSO login page (redirect loops, slow IdP, MFA). Expected: the login identified as the bottleneck.
2. Switch the Adobe data collection to the User Management API with a proper API credential. Expected: the browser path removed.
3. If the browser path is truly required, lengthen timeouts and pre-warm the SSO session, but treat this as a workaround. Expected: the flaky path stabilized as much as possible.
4. Re-run the audit. Expected: Adobe data collected without the login wait.

## When to use
- The Adobe audit depends on a browser SSO login
- The login times out under automation
- The audit silently skips Adobe on failure

## When not to use
- The API credential lacks permissions (an API auth problem)
- The console login works but data extraction fails (a scraping problem)
- You have no API access (request it; it is the right fix)

## Tool compatibility
Adobe Admin Console and User Management API.

### Variant phrasings
### SSO login works manually but not in Playwright
Automation changes the browser fingerprint and timing. The API avoids all of it.

### audit skips Adobe silently
Make the skip loud: fail or alert when a source is skipped so it gets fixed.

## Why it happens
SSO logins involve redirects, JavaScript, and sometimes human steps, all of which are hostile to automation timeouts. The API exists precisely to avoid this.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_dvVWDZsK8yE38u2Qyu8SrA