USER_NEW trigger ignores streams from list after certain point

[dvwh]

Tested on version 3.2, it seems that the USER_NEW trigger does not send data to the script (the trigger fails to trigger), in my case to https endpoint, specifically after a certain entry in the stream list that applies to the trigger definition. For example, trigger definition:

"triggers":{
    "USER_NEW":[
    {
      "default":"0",
      "handler":"https://serv1.tv:4443/ms/auth",
      "streams":[
        "nnnnnnnnn1", "nnnnnnnnnnn2", "nnnnnnnnnnnnn3", "nnn_nn4", "nnn_nnn_nnnnnn5", "nnnnnnnnnnnnnnn6", "nnnnnnnnnnnnnnnnn7", "nnnnnnnnnnnnnnnnnn8", "nnnnnnnn9", "nnnnnnnn_10", "nnnnnnnnnn11", "nnnnnnnnnn12", "nnnnnnnnnn13", "nnnnnnnnnn14", "n15", "nnn_16", "nnn_17", "nnn18"
      ],
      "sync":true
    }
    ]
}

All streams except "nnn_17, "nnn18" trigger USER_NEW. This trigger definition works fine:

"triggers":{
    "USER_NEW":[
    {
      "default":"0",
      "handler":"https://serv1.tv:4443/ms/auth",
      "streams":[
        "nnnnnnnnn1", "nnnnnnnnnnn2", "nnnnnnnnnnnnn3", "nnn_nn4", "nnn_nnn_nnnnnn5", "nnnnnnnnnnnnnnn6", "nnnnnnnnnnnnnnnnn7", "nnnnnnnnnnnnnnnnnn8", "nnnnnnnn9", "nnnnnnnn_10", "nnnnnnnnnn11", "nnnnnnnnnn12", "nnnnnnnnnn13", "nnnnnnnnnn14", "nnn_15", "nnn_16"
      ],
      "sync":true
    }
    ]
}

Seems like it hits some kind of character limit? This limitation can be bypassed by creating additional, same type triggers with stream list entries that did not work in previous definition. Also, it work fine when stream list is empty (applies to all streams), but that does not work for my case. This limit complicates trigger definition generation. What is the character limit, and is there meant to be one?