Stream Selection anomaly
I have a Stream Selector stage with the following condition:
${record:value('/create-user_response/data[0]/request_results/this_does_not_exist') == 'failure'}
The field at the end of the path DOES NOT EXIST, yet the pipeline doesn't error out completely and actually passes the record to a continuing processor stage instead of an error stage that its supposed to send to.
Any insight would be greatly appreciated.
Thanks.
Per Jeff's update request...
For some reason now the behavior has changed and the Selector is sending to the proper stream (don't know why it changed as before is was definitely sending it to the default) However, I'm still not sure why it allowed the records to be sent to Stream 1 when the field in the the condition does not exists.
Screen shot (redacted a bit for privacy sake):
As a sanity check, can you trigger this in a preview? In other words, you run a preview that shows the record entering the stream selector, and shows the output going down the wrong lane?
Jeff, yes when running in preview it sends to the wrong selection branch. Thx.
Please update your question showing screenshots of the configuration, and incoming record into the stream selector, and outgoing record down the incorrect path
Please paste the stage configuration for your stream selector too. I am noticing from the first line of your preview screenshot (the "Condition" string) that it's different from what you pasted in the question.