Login takes seconds: Actions with network calls, Rules ordering, timeouts

TL;DR: Symptom: login completes but takes 5+ seconds. Cause: extensibility code doing network I/O per login, often sequentially. Verify Time three consecutive logins; p95 under ~1.5s for database connections. Keep the timing check in your release checklist whenever an Action changes.

The error

login completes but takes 5+ seconds. Cause: extensibility code doing network I/O per login, often sequentially. Verify Time three consecutive logins; p95 under ~1.5s for database connections. Keep the timing check in your release checklist whenever an Action changes.

The fix

TL;DR: Symptom: login completes but takes 5+ seconds. Cause: extensibility code doing network I/O per login, often sequentially. Verify Time three consecutive logins; p95 under ~1.5s for database connections. Keep the timing check in your release checklist whenever an Action changes.

The fix

1. Actions making HTTP calls per login (enrichment APIs, CRM lookups) with no timeout or cache. Two Actions each calling out serially doubles it.
2. Legacy Rules with the same pattern, plus Rules run before Actions in mixed pipelines.
3. Custom database scripts with slow bcrypt rounds or external calls.
4. Social/enterprise IdP latency (out of your control, but measurable).
5. Actions > your Action > Real-time Logs: run a test login and watch execution time per Action.
6. Tenant logs: compare the login event's date with the authorize start; the gap is pipeline time.
7. Disable Actions one by one (or run the flow with the Action removed) and re-time. Binary search the slow one.
8. Cache enrichment data (per user, TTL hours) instead of fetching per login.
9. Set aggressive timeouts on outbound calls (2-3s) and fail open or closed deliberately, not by hanging.
10. Move non-critical work (analytics, CRM sync) to a post-login async path or a log-stream-triggered job, not the login pipeline.
11. Migrate remaining Rules to Actions; the mixed pipeline adds overhead.

When to use this

• You are seeing this exact error message; match the block above, not just part of it.
• The failing call matches the scenario in the title: Login takes seconds.
• You want the fastest verified fix before digging through logs.

When not to use this

• Your error text differs from the block above; close cousins often have different causes.
• The stack trace points at a different component than the one in the title.
• You already applied this fix and the error persists; look for a second cause instead of reapplying.

Compatibility

• Not pinned to a specific version; follows current Login behavior.

Auth0's Actions docs describe the real-time logs and testing tools for Actions. The Actions extensibility model and flow execution are documented in the Actions overview. Verified against live docs 2026-09-26.