Operations

Work in progress

This page discusses new functionality that has replaced some of the existing architecture of Action Links, but is still being developed. The documentation is therefore a work in progress.

Error handling

Action Links handles errors that occur server-side (i.e. when processing operations) in one of three ways:

• Response Error: If the error has been returned by an integration API, successive operations will be completed and the error will be surfaced to the errors object of the [operation][resource] object.

• Configuration Error: If the error is due to an issue with your integration or Link setup, e.g. the credentials for the integration are invalid or a field has an invalid Handlebars value, we'll return a generic configuration error and attempt to log the error such that you can view it from the Edit Link page in the CMS. Note, these errors will prevent your Action Link from loading (if occurring in a pre-action layer) or prevent post-action operations from continuing until you resolve the underlying issue. This is to protect your Link from a potential security vulnerability exposed by the error.

• Unknown Error: If the error has not been caused by a known issue, Action Links will log these and return a generic error. If you are encountering an error that you are unable to view from the Edit Link page in the CMS, get in touch and we'll look into it.

Handling Response Errors

Some APIs return errors in the course of their expected behaviour, for example as a way of identifying that legitimately requested data does not exist. To avoid such errors interrupting the flow of your operations and to enable you to handle them as appropriate, we return a null value in place of the data requested and surface the error.