Skip to main content


Laurence MorganAbout 1 min


Checks state of each function in a pipeline and exits block on error


trypipeerr checks the state of each function and exits the block if any of them fail. Where trypipeerr differs from regular tryerr blocks is trypipeerr will check every process along the pipeline as well as the terminating function (which tryerr only validates against). The downside to this is that piped functions can no longer run in parallel.


trypipeerr { code-block } -> <stdout>

<stdin> -> trypipeerr { -> code-block } -> <stdout>


trypipeerr {
    out "Hello, World!" -> grep: "non-existent string" -> cat
    out "This command will be ignored"

Formated pager (less) where the pager isn't called if the formatter (pretty) fails (eg input isn't valid JSON):

func pless {
    -> trypipeerr { -> pretty -> less }


A failure is determined by:

  • Any process that returns a non-zero exit number
  • Any process that returns more output via STDERR than it does via STDOUT

You can see which run mode your functions are executing under via the fid-list command.

See Also

  • Schedulers: Overview of the different schedulers (or 'run modes') in Murex
  • catch: Handles the exception code raised by try or trypipe
  • fid-list: Lists all running functions within the current Murex session
  • if: Conditional statement to execute different blocks of code depending on the result of the condition
  • runmode: Alter the scheduler's behaviour at higher scoping level
  • switch: Blocks of cascading conditionals
  • try: Handles non-zero exits inside a block of code
  • tryerr: Handles errors inside a block of code
  • trypipe: Checks for non-zero exits of each function in a pipeline
  • unsafe: Execute a block of code, always returning a zero exit number

This document was generated from builtins/core/structs/tryerr_doc.yamlopen in new window.

Last update:
Contributors: Laurence Morgan