What happened
What this says
Current to 14 Oct 26Cian Farrell reported policy database connector timing out during onboarding setup. Every sync attempt timed out. Bethan Lister suggested increasing timeout setting to 60 seconds.
Problem: Cian Farrell was setting up a policy database connector but every sync attempt timed out. This blocked policy data ingestion during onboarding. Connection timeouts usually indicate database responsiveness or network issues.
Handling: Bethan Lister diagnosed the issue and recommended increasing the connector timeout setting to 60 seconds, a standard troubleshooting step for slow database responses.
Watch: Early-stage customer with blocking setup issue needs quick resolution to avoid delaying go-live. No confirmation shown that timeout increase resolved the problem.
Details
Updated 9 Oct 26Trail
- created · Cian Farrell 13 Nov 2025 10:28We're setting up the connector to our policy database but it's failing to sync. The connection string looks correct to us. Every attempt times out with the error message "connection timeout". This is blocking us from getting policy data into the brain. Can you help us troubleshoot this?
- public_reply · Bethan Lister 13 Nov 2025 12:15Hi Cian, Just so I've got this right, the connector is timing out when it tries to reach the policy database. Connection timeouts usually happen if the database is slow to respond or there's a network issue. Can you try increasing the timeout setting in the connector config to sixty seconds and see if that helps? Thanks, Bethan
- status_change · 23 Nov 2025 23:59