Why does errored() return a false result in sub command?

[static-moonlight]

pipeline:
  processors:
    - switch:
      - check: [...]
        processors:
          - [...]
      - processors:
        - resource: processor_1 # Processor that fails
        - switch:
          - check: errored() # <-- falsely returns false
            processors:
              - [...]
    - switch:
      - check: errored() # <-- returns true, as expected
        processors:
          - [...]

When I have a structure, like above, with a processor that can fail, within a sub structure, then the check in the same sub structure does not work correctly, because the function errored() always return false even when the processor_1 failed, while it should actually return true. The 2nd switch however, back on the root level, works as expected. Here the errored() check would return true.

Why is that? Why can't I check for errors while still in a sub structure?

EDIT: And while I'm at it: Can I manually set something (call a function, set a certain metadata value, ...) to make the errored() function return true?

[mihaitodor]

Hi @static-moonlight I'd need to be able to reproduce this, so please share a self-contained example using a generate input.

Can I manually set something (call a function, set a certain metadata value, ...) to make the errored() function return true?

You should be able to use throw("some error") in a mapping processor.

[static-moonlight]

I wanted to check first if this is intentional, maybe some fundamental design philosophy or something. Since you are implying that this is not the case, I could open an actual issue with a proper example, yes?

[mihaitodor]

Yes, of course!