Azure SQL Database: Error 40613 on first connection to a paused serverless database

TL;DR

Set Connection Timeout=60 in the connection string (the 30-second default turns every cold start into a failure) and retry 40613/40501/10928/10929 with exponential backoff on a fresh connection, because the old handle is dead. Do not retry 18456 (wrong password) or 208 (missing table): those are permanent and retrying just slows a clear failure.

The error

Error 40613 on first connection to a paused serverless database

Fix

1. Set Connection Timeout=60 in the connection string (the 30-second default turns every cold start into a failure) and retry 40613/40501/10928/10929 with exponential backoff on a fresh connection, because the old handle is dead. Expected: You get the expected result; the problem is gone.

2. Re-run the original operation and confirm the error is gone. Expected: no error, normal output.

When to use

• You hit this exact error with Azure SQL Database.
• The symptom matches: Error 40613 on first connection to a paused serverless database.

When NOT to use

• A different error message from Azure SQL Database; the cause here is specific to this error.
• Unrelated Azure SQL Database issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Azure SQL Database. Source: https://github.com/stepvda/railpulse_cloud.

Variant phrasings

Error 40613 on first connection to a paused serverless database

Why it happens

The first connection of the day to an Azure SQL serverless database fails with Error 40613 (Database is not currently available) while the platform resumes it, which takes 30-60 seconds. A few seconds after resume it may briefly throttle (40501, 10928/10929). None of these are bugs.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/stepvda/railpulse_cloud

Source: The first connection of the day to an Azure SQL serverless database fails with Error 40613 (Database is not currently available) while the platform resumes it, which takes 30-60 seconds. A few seconds after resume it may briefly throttle (40501, 10928/10929). None of these are bugs.

Verified resolution: [field notes]: Set Connection Timeout=60 in the connection string (the 30-second default turns every cold start into a failure) and retry 40613/40501/10928/10929 with exponential backoff on a fresh connection, because the old handle is dead. Do not retry 18456 (wrong password) or 208 (missing table): those are permanent and retrying just slows a clear failure.

Source URL: https://github.com/stepvda/railpulse_cloud