BuildShipBBuildShip
Powered by
solS
BuildShip•16mo ago•
4 replies
sol

Wondering about Best Practices around error status codes.

I'm noticing that a lot of my "expected" return status codes like 404 are being reported as "Failed" red dots in the logs, when they aren't in fact errors, but just states that are handled by the app. (example: promo code note found results in a 404). In terms of REST, I believe this to be best practice (?), to use the status codes to represent the api status. Ideally, I'd like "Failed" to appear only for return error 500 statuses. And this would make the most sense to me anyway - why would a 404 be a typical error condition, versus just a normal state of the api?

Am I missing something? Is there a better way to do this?
BuildShip banner
BuildShipJoin
Join founders, builders, devs using Low-code / No-code to create backend, APIs, scheduled Jobs, automation, AI workflows
7,971Members
Resources
Recent Announcements

Similar Threads

Was this page helpful?

Similar Threads

Awaiting Status
PauPPau / ❓・buildship-help
7mo ago
Pro Plan's Status Page
RFARRFA / ❓・buildship-help
4mo ago
Rate exceeded - Status: 429(Failure)
kishchanKkishchan / ❓・buildship-help
3y ago
Webhook with the Workflow Status
Murilo RavaniMMurilo Ravani / ❓・buildship-help
3y ago