Diagnose a failing Server Connect request

Use the response status and action output to locate a failing request.

Also called: API error, server error, 404, 500, validation error.

Capture one failing request

Open Preview and reproduce the problem once. In Network, select the Server Connect request. Note its URL, method, status, submitted inputs and response. These observations determine which configuration to inspect.

404: check the action path

Confirm that the action exists in the current project and the page component selects it. Use the current local or deployment target URL. Check rewritten routes and the action path before renaming parameters.

400: inspect submitted inputs

Compare the actual submitted names and types with Inputs in the action. Check required values, numeric conversion, empty fields and validation messages. A form field ID and its submitted name are different settings.

401 or 403: check authentication and permissions

Confirm that the browser has the expected login session and that the action uses the intended Security Provider and permission rule. Test with the correct user role. Keep authorization enforced in the server action.

500: find the failing server step

Inspect the server-side error details in your local development environment. Check the database connection, missing files, invalid expressions and the last successful workflow step. Reproduce with one known input and keep diagnostic details out of production responses.

Retest both outcomes

Run the corrected request with valid input and verify its expected JSON. Then submit invalid input and confirm the page displays a usable error without treating the request as a success.

Check your result

The request or table behaves correctly for both valid data and an empty or invalid result.