FLAT
CouperSevenval TechnologiesDocker ImageGithub
master
master
  • Changelog
  • FLAT
  • Administration
    • Configuration
    • Docker
    • Logging
  • Cookbook
    • Using the Built-in Mocking
    • Performing Additional Checks on JWT Access Tokens
    • Logging Custom Fields
    • Using Environment Variables
    • Handling Errors with an Error Flow
    • File Serving
    • Forwarding a Request to an Upstream API
    • Extracting Common Initialization Flow Tasks
    • Encoding and Decoding JWT
    • Passing Header Fields to the Client
    • How can I pass an arbitrary header field to an upstream system?
    • Performing Additional Checks on JWT Access Tokens
    • Proxying requests to Upstream APIs
    • Increasing the Request Timeout
    • How can I see what the client requested?
    • Using Swagger UI for API Documentation
    • Testing API Requests
    • Testing with Backend Requests
    • Testing Templates
    • Sending POST Requests
    • Processing Upstream Responses
    • Protecting Access using JWT Tokens
  • Reference
    • Configuration
    • Debugging
    • flat CLI
    • Flow
    • Variables
    • OpenAPI / Swagger Integration
    • OpenAPI
      • CORS - Cross-Origin Resource Sharing
    • OpenAPI
      • Differences from Swagger
    • OpenAPI
      • Mocking
    • OpenAPI
      • Routing
    • OpenAPI
      • Security
    • OpenAPI
      • Upstream APIs
    • OpenAPI
      • Validation
    • Flow Actions
      • assert Action
      • auth Action
      • backend-flow Action
      • copy Action
      • debug Action
      • dump Action
      • echo Action
      • error Action
      • eval Action
      • log Action
      • nameshave Action
      • pass-body Action
      • proxy-request Action
      • regex Action
      • request Action
      • requests Action
      • serve Action
      • set-config Action
      • set-env Action
      • set-response-headers Action
      • set-status Action
      • sub-flow Action
      • template Action
      • test-request Action
      • xslt Action
    • Functions
      • apply-codecs()
      • array-reverse()
      • array()
      • base64-decode()
      • base64-encode()
      • body()
      • calc-signature()
      • capitalize-first()
      • content()
      • decrypt-xml()
      • decrypt()
      • encrypt()
      • ends-with()
      • file-exists()
      • fit-document()
      • fit-log()
      • fit-serialize()
      • get-log()
      • has-class()
      • html-parse()
      • join()
      • json-doc()
      • json-parse()
      • json-stringify()
      • json-to-csv()
      • json-to-xml()
      • jwt-decode()
      • jwt-encode()
      • ldap-lookup()
      • ldap-query()
      • lookup()
      • matches()
      • md5()
      • replace()
      • sort()
      • split()
      • tolower()
      • toupper()
      • trim()
      • unixtime()
      • urldecode(), url-decode()
      • urlencode(), url-encode()
      • uuid3() and uuid4()
      • verify-signature()
      • verify-xmldsig()
      • xml-parse()
      • xml-to-json()
    • Templating
      • {{,}}
      • Comment {{// …}}
      • Dot {{.}}
      • Conditional `{{if <condition>}} … {{elseif <condition> }} … {{else}} … {{end}}
      • loop
      • ?? Operator
      • Object XML Notation (OXN)
      • Pair Producer {{: …}}
      • Placeholder
      • Template Variables
      • with
    • Testing
  • Tutorial
Powered by GitBook
On this page
  • Error Properties
  • Status Code
  • Fixed message shortcut
  • Logging
  • See also

Was this helpful?

  1. Reference
  2. Flow Actions

error Action

Previousecho ActionNexteval Action

Last updated 4 years ago

Was this helpful?

The error action provides a simple and consistent way to handle errors throughout the configuration.

It terminates the flow, sets its body template result as and calls the , if configured, or sends the with the body template result as the value of the error property.

In its simplest form, an error is triggered like this:

<error/>

To make errors more useful, they should contain a message:

<error>
{
  "message": "Upstream system sent unusable data"
}
</error>

Error Properties

The action body contains a constant JSON string or a representing a JSON object. The object will be assigned to the $error variable.

The following properties of the $error object are optional, but must have the specified type if set. If not set, they will receive the following default values:

  • message: string, default: 'FlowError'

  • status: integer between 100 and 599, default: 500

  • code: integer between 0 and 9999, default: 5000

  • info: array of string, default: ["Flow Error triggered"]

Additional properties are allowed. They will be accessible in the Error Flow. The following example includes the URL in $error/url:

<error>
{
  {{: $request/url }}
  "message": "Upstream system sent unusable data",
  "status": 502,
  "code": 4711
}
</error>

Status Code

The status property will be used as the HTTP response status code. The status code may alternatively be defined with the optional status attribute.

<error status="403"/>
<error status="502">
{
  "message": "Upstream system sent unusable data"
}
</error>

Fixed message shortcut

If the action body is a string constant (it must be enclosed in double quotes), its value will be assigned to the $error/message property. This is a handy shortcut to trigger simple errors with fixed messages:

<error status="502"> "Upstream system sent unusable data" </error>

Logging

{
  "timestamp": "2020-05-19T16:27:46+00:00",
  "type": "flat_alert",
  "requestID": "XsQJAMvNgp1P2qKAxKmdaAAAAAI",
  "topic": "error",
  "message": "Upstream system sent unusable data"
}

See also

The error emits an event with the error topic and the given message:

(Cookbook)

Handling Errors
JSON template
error log
Error Flow
error flow
$error
$error
system error document