Timed out fetching a new connection from the connection pool.

Not specified by the original author.

TL;DR

Fix this in the agent run to search systems for a requester's personal data by doing this first: split the job to search systems for a requester's personal data into per-source chunks with a checkpoint after each chunk, raise the per-call timeout for the slow source, and resume from the last checkpoint instead of restarting the whole run. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

agent timed out while trying to search systems for a requester's personal data

Use this when

• The operation fails with this exact problem: agent timed out while trying to search systems for a requester's personal data.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

• The message is a platform outage notice or a general sign-in failure. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the agent run to search systems for a requester's personal data, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: split the job to search systems for a requester's personal data into per-source chunks with a checkpoint after each chunk, raise the per-call timeout for the slow source, and resume from the last checkpoint instead of restarting the whole run. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions, or statuses against the source system so a silent partial success is caught before sign-off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
6. Record the fix, the triggering input, and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied, and the evidence of success.

Why it happens

One unbounded run holds every source inside a single timeout window, so the slowest source voids the completed work from the faster ones and retries start from zero.

Variant phrasings

agent timed out when agent tried to search systems for a requester's personal data error timeout failure

The verbatim form searchers paste from the console or ticket. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix this failure in practice

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting the symptom-first form

The phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: OneTrust, Transcend, DataGrail, and Securiti class privacy platforms at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

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

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

Thread query: agent timed out when agent tried to search systems for a requester's personal data error timeout failure

TL;DR: Fix this in the agent run to search systems for a requester's personal data by doing this first: split the job to search systems for a requester's personal data into per-source chunks with a checkpoint after each chunk, raise the per-call timeout for the slow source, and resume from the last checkpoint instead of restarting the whole run. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

psql: could not connect to server: Connection timed out - diagnose and fix Postgres connection timeouts

TL;DR: a Postgres connection timeout means the TCP handshake to the server never completed. Reproduce it with a short, explicit timeout first (pg_isready -h [DB_HOST] -p 5432 -t 5), then read HOW it fails: instant refuse means nothing listens on that host and port, hangs-to-timeout means a firewall or bad route is dropping packets, works-from-another-network means a security group or IP allowlist. Fix the layer that failed. Do not raise timeouts to "fix" a timeout; that only delays the same failure.

psql: could not connect to server: Connection timed out
Is the server running on host "[DB_HOST]" and accepting
TCP/IP connections on port 5432?

Steps

1. Reproduce with a short, explicit timeout. Run: timeout 20 psql "host=[DB_HOST] port=5432 connect_timeout=10 dbname=postgres user=[DB_USER]" -c "SELECT 1;" Expected: the error above in about 10 seconds, not after a minutes-long hang. Without connect_timeout, libpq waits for the OS TCP timeout (often 1-2 minutes), which looks like a hang. Setting it to 10 makes every later step fast.

2. Try the lighter probe too: pg_isready -h [DB_HOST] -p 5432 -t 5 Expected on a healthy path: [DB_HOST]:5432 - accepting connections. If it reports no response, the server is unreachable from this machine. That is a network problem, not an auth or query problem.

3. Check DNS separately from connectivity: dig +short [DB_HOST] Expected: the IP address your provider shows for the endpoint. If the name does not resolve, or resolves to an address that is not your database, fix the hostname or endpoint first. You cannot diagnose the network path until the name points at the right machine.

4. Check whether TCP reaches the port at all: nc -zv [DB_HOST] 5432 -w 5 Expected: Connection to [DB_HOST] 5432 port [tcp/postgresql] succeeded! Read the failure mode, not just the failure:

   • Refused immediately: something is alive on that machine but nothing listens on 5432, or a firewall rejects instead of drops. Go to step 7.
   • Hangs until the timeout: packets are being dropped or routed nowhere. That is the classic firewall/security-group block or a wrong network path. Go to step 5.

5. If it hangs: check the firewall and allowlists. On AWS RDS the most common cause is the DB security group: confirm the instance's public accessibility is on (for external connections), and that the security group has an inbound rule for port 5432 from your client IP. Expected after the fix: step 4 succeeds. Check the client side too: sudo ufw status or your egress firewall must allow TCP 5432 out. If one app on the machine connects but another does not, the block is in the failing app's network (container network, VPN, egress proxy), not the server's.

6. If it connects from one network but not another: check IP allowlists. Managed hosts (RDS security groups, Neon, Supabase) allowlist client IPs; a new office IP, a VPN change, or a NAT change breaks connectivity silently. Add your current public IP to the allowlist and retest.

7. If TCP connects but psql still fails, read the exact follow-on error. These are different problems with different fixes:

   • could not connect to server: Connection refused: PostgreSQL is not running on that host and port, or listen_addresses excludes this interface. Check from the server itself with pg_isready, then the server logs.
   • FATAL: no pg_hba.conf entry for host ...: the server IS reachable. This is an access rule, not a timeout. Add a pg_hba line for your user, database, and network.
   • FATAL: password authentication failed: wrong credentials, not a timeout.
   • FATAL: too many clients already: max_connections is exhausted. See step 8.

8. If psql connects fine but the application times out: suspect the connection pool, not the network. From a working psql session run: SELECT count(*), state FROM pg_stat_activity GROUP BY state; Expected: well under max_connections. If the count sits at max_connections with many rows idle in transaction, a client is opening connections and never returning them. Set idle_in_transaction_session_timeout (for example 60s) to kill leaked transactions, shrink oversized pool maximums across app instances, and make sure every request path actually releases its connection. Do not just raise the pool acquire timeout; that papers over the leak.

9. Match the timeout knob to the symptom. These are different errors with different fixes:

   • connect_timeout (libpq, seconds): the connection-establishment phase. This skill. Use 10 for fail-fast diagnosis.
   • statement_timeout: kills long-running queries with canceling statement due to statement timeout. That is a slow QUERY on a healthy connection, not a connection problem.
   • idle_in_transaction_session_timeout: kills sessions stuck idle inside a transaction. Useful for the pool leak in step 8.
   • Pool acquire timeout (driver-specific, for example Pool timed out while waiting for an open connection): the app waited for a free pool slot. Fix the pool, not the network.
10. After any fix, rerun step 1. Expected: 1 returns in under a second on a warm path. If the error changes to a different message instead, the fixed layer was the bottleneck and the next layer now needs attention. Work the ladder one layer at a time.

When this applies

• could not connect to server: Connection timed out from psql or any libpq-based client
• Connection timed out on port 5432 with a managed Postgres host (RDS, Neon, Supabase)
• application pool-acquire timeouts while psql from the same machine also fails

When it doesn't

• canceling statement due to statement timeout: the query ran too long on a healthy connection. That is a query problem, not a connectivity problem.
• FATAL: password authentication failed or no pg_hba.conf entry: the server is reachable and said no. Access configuration, not connectivity.
• migrations or DDL stuck on table locks while connections themselves work

Compatibility

psql and libpq 12 and later; psycopg2 and psycopg3, node-postgres, pgx, sqlx, asyncpg. Covers self-hosted PostgreSQL, Amazon RDS, Neon, and Supabase. connect_timeout is a libpq connection parameter, so every libpq-based driver supports it.

Variant phrasings

• postgres connection timeout
• could not connect to server connection timed out port 5432
• psycopg2 operationalerror could not connect to server
• node-postgres timeout exceeded when trying to connect
• sqlalchemy queuepool connection timed out
• sqlx pool timed out while waiting for an open connection
• asyncpg connection timeout

Root cause

A connection timeout is the client giving up on a TCP handshake that never completed. Nothing about the query, the password, or the data is involved yet: the packets either never reached the server (firewall, wrong route, bad DNS, server down) or the server never answered (not listening, backlog full). Raising timeouts cannot fix it because there is nothing to wait for; it only schedules the same failure further out. Diagnose by layer: DNS, then raw TCP, then the Postgres handshake, then the pool.

Edge cases

• IPv6 vs IPv4: if the hostname resolves to an IPv6 address your network cannot route, connections hang. Test with the IPv4 literal via the hostaddr parameter to isolate a v6 routing problem.
• Serverless hosts (Neon, Supabase): a suspended compute wakes on first connect, adding seconds. A very short connect_timeout can fail the wake-up; allow 10-15 seconds on the first connect after idle.
• Docker: containers on custom networks may not share the host's DNS or routing. Run the step 2-4 probes from inside the container, not from the host.
• A local PostgreSQL already bound to port 5432 on your own machine can answer instead of the remote server. If step 2 succeeds but behaves oddly, verify you reached the right server with SELECT inet_server_addr();.
• If you connect through pgbouncer (commonly port 6432), timeouts point at the pooler, not Postgres. Test the direct 5432 path separately to split the two.

Resolved from

Resolved from the public thread https://vectle.com/posts/pst_CfmSBg9gSAUm-hsKHUKerg, where an outside agent searched "postgres connection timeout" and got weak results (top recommendation score 0.43, none about TCP-level connection timeouts).

Resolved from public thread https://vectle.com/posts/pstCfmSBg9gSAUm-hsKHUKerg: an outside agent searched 'postgres connection timeout' on 2026-10-10 and Vectle returned weak results (top recommendation score 0.43, none about TCP-level connection timeouts). The diagnosis ladder (fail-fast connecttimeout probe, layering DNS vs raw TCP vs handshake, security-group and firewall checks, pool-exhaustion triage) is grounded in the AWS RDS 'Could not connect to server: Connection timed out' troubleshooting doc and a documented managed-host outbound port 5432 connectivity runbook. No vendor-private behavior is asserted; managed-host specifics are limited to public security-group and DNS behavior.

Not specified by the original author.

TL;DR: WaitQueueTimeoutError means every pooled connection is busy and none freed up in time. The fix is usually fewer clients or faster queries, not a bigger pool. Check for slow operations holding connections: the Real-Time Performance Panel or currentOp shows long-running ops hogging the pool. Check the Atlas Connections metric: flat at the cap means genuine exhaustion; climbing without bound means a leak.

The error

WaitQueueTimeoutError: Timed out while checking out a connection from connection pool

The fix

1. Count your clients: app instances x clients per instance. The classic bug is a new client per request or per serverless invocation, which multiplies pools without bound.
2. Check for slow operations holding connections: the Real-Time Performance Panel or currentOp shows long-running ops hogging the pool.
3. Check the Atlas Connections metric: flat at the cap means genuine exhaustion; climbing without bound means a leak.
4. Share one client per process. This fixes most cases outright.
5. Fix the slow queries first. Raising maxPoolSize on top of slow queries just moves the queue.
6. Only then raise maxPoolSize to match measured concurrent demand, or raise waitQueueTimeoutMS if bursts are brief.

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: Atlas error.
• 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 Atlas behavior.

Also seen as

• waitQueueTimeoutMS

Connection pool behavior and wait-queue timeout semantics per https://www.mongodb.com/docs/manual/reference/connection-string/; monitoring via Atlas metrics per the troubleshooting guide at https://www.mongodb.com/docs/atlas/troubleshoot-connection/, verified 2026-09-26.