Error Handling
This page outlines error patterns, debugging tips, and all possible errors for quick troubleshooting to aid developers in building resilient applications. API errors in Webflow may be a result of a number of scenarios including but not limited to insufficient Webflow entitlements, user role abilities, and more.
Error patterns
The Designer API employs a structured format for exceptions, ensuring you have clear and actionable information at your disposal. Here’s what you can expect in the event of an error:
Cause Tag (err.cause.tag)
: Accompanying each error message is a consistent, unchanging cause tag. These tags describe a unique error type for the purpose of programmatically distinguishing between different error scenarios and responding accordingly.
Message (err.message)
: A descriptive sentence designed to provide insight into what went wrong. The wording of this message may change over time to clarify or reflect updated functionality within the Designer API.
List of errors
This section provides a detailed list of error cause tags you might encounter while interacting with the Designer API.
How to handle errors
Apps need to manage errors gracefully to maintain a seamless user experience. See the approaches below for a few patterns on how to handle errors if they arise when working with Designer APIs.
Using try/catch for error handling
The try/catch block is seamlessly integrated with async/await syntax, offering a straightforward way to catch exceptions as demonstrated:
Notifying users of an error
By utilizing the webflow.notify
method, you can send a notification directly to the user within Webflow that acknowledges the error and also, when feasible, provide guidance on resolving it. This proactive approach helps maintain trust and ensures users aren’t left in the dark, improving their overall experience and satisfaction with your application.