On this page
Troubleshoot MiniUp Functions
Diagnose a Function failure by checking the request status, access mode, method, path, and whether the intended code has been published. A draft change does not change the live endpoint.
Match the symptom to the next check
| Symptom | What to check |
|---|---|
| 401 Unauthorized | Required API key, or signed-in membership for a Site Members Function |
| 403 Forbidden | Member role, linked Site, and the Function’s own authorization rules |
| 404 Not found | Copied endpoint, slug, linked Site, and route implemented by your handler |
| 405 Method not allowed | Allowed methods and the handler’s method check |
| 429 or quota message | Function call usage, remaining allowance, and reset date |
| Browser-only failure | Allowed Web Origins; use same-origin URLs for Site Members Functions |
| Preview succeeds but live code differs | Publish the current draft and retest the live endpoint |
| Secret change has no live effect | Publish again to apply the current Secret set |
| Dependency error | Approved Trusted ESM source, import syntax, version, and supported module |
| Function error / 500 | Input parsing, handler exceptions, and external service failures |
Debug one request at a time
- Open the Function and confirm its status and last deployed information.
- Reproduce the failing method, path, query, headers, and body in Test using safe test data.
- Check whether the handler returns an error or the request fails before it reaches your app logic.
- Correct the relevant setting or code. Test again, then publish code changes.
- Verify from the intended caller: trusted server, public browser, or signed-in linked Site.
Example: /bootstrap returns 404
/bootstrap only exists if your Function implements it. Check url.pathname.endsWith("/bootstrap") and confirm the handler was published. Then call /api/functions/my-app-api/bootstrap from the correct linked Site.
Avoid hiding failures
A failed data call should show a visible error and retry option. Do not show an empty successful dashboard for an authorization failure. Keep credentials and private service responses out of browser error messages.