When a task renders an error object, the task run will be marked as failed. This is a good way to communicate an intentional failure to the user, when your Liquid code detects a certain condition. A task that renders an error object during preview will prevent the user from saving it in that state, which means that error objects are a good way to enforce additional validation on task options.
An error object is a plain JSON object, having the following structure:
The error details can be any JSON value. This value will be represented to the user as the reason for the task failing.
Error objects are most easily generated using the error tag.