Database API Builder (DAB) Stopped working with SWA

Eric B 0 Reputation points
2025-06-05T00:29:30.35+00:00

Database API Builder (DAB) stopped working across two of my SWA instances. Is it working or is it something on my side.

I get error 500 sometimes other times I get error 400 Bad Request

Azure Static Web Apps
Azure Static Web Apps
An Azure service that provides streamlined full-stack web app development.
1,173 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Suwarna S Kale 3,316 Reputation points
    2025-06-05T02:21:27.9166667+00:00

    Hello Eric B,

    Thank you for posting your question in the Microsoft Q&A forum. 

    The intermittent 500 and 400 errors in your Database API Builder (DAB) across multiple Static Web Apps (SWA) instances suggest either a service disruption or configuration issue. First, check Azure Status for any ongoing incidents with DAB or dependent services. 

    Key troubleshooting steps: 

    • Verify your connection strings and database permissions haven't expired or changed 
    • Review recent deployment logs for schema changes that might conflict with DAB 
    • Test with a minimal API endpoint to isolate whether the issue affects all endpoints 

    If basic checks show no problems, redeploy your DAB configuration and enable detailed logging to capture the root cause. The mixed error codes often indicate either authentication problems (400) or backend processing failures (500). 

    If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated. 


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.