Error lookup
Find an error from a failed run by its code or its sentence, and read what causes it and what to do next on its errors page.
Every code a run can fail with has a line on its errors page, under the app or service that raised it.
What you can paste
The code is under Show details in a failed step's Output, often followed by a colon and the details of that one run, and in the failed run's row on Runs. The sentence leads the Output.
| You paste | For example | It opens |
|---|---|---|
| The code | EXPRESSION_ERROR | That code's line |
| The line in Show details | EXPRESSION_ERROR: field 'message': formatDate(): a string of 9 characters is not a valid ISO-8601 date | The line of the code in it |
| The sentence | An expression in a node's settings could not be evaluated — check the field it names. | The line of the code it belongs to |
| Part of the sentence | could not be evaluated | The line of the code whose sentence holds it, or a list when several do |
How it behaves
- A code works alone in capitals or lower case; inside a longer line, in capitals, as the run shows it.
- A sentence works whole or in part, with or without its full stop. A part needs at least 16 characters.
- One match opens; several give a list to pick from; with none, the lookup says so and links the errors pages.
- What you paste stays in your browser: the lookup sends it nowhere.
Common mistakes
- Pasting only what comes after the code. That part holds one run's details and changes from run to run. Paste the code, or the sentence.
- Copying part of a code.
INVALID_ADDRESSmatches nothing;SES_INVALID_ADDRESSdoes. - Looking up an
HTTP_code. It is the status the system your flow called answered, such asHTTP_404: look it up in that system's documentation.