I'm splitting up a set of text by lines and then parsing out the lines in Laserfiche Cloud workflow.  I've tried splitting the lines various ways using pattern matching.  Both *. and [^\r\n]+ work fine when the data on each line is small.  However, once the data on a line goes past 96 characters, I get some weird behavior.

To replicate, add a pattern matching activity to a workflow.  Use one of the above regular expressions.  Click on "test" and put in the following for the test data:

123456789123456789123456789123456789123456789123456789123456789123456789123456789123456789123456
Next Line

Run the test and it should work as expected.  Now, replace any of the digits with a space character:

123456789123456789123456789123456789123456789123456789123456789123456789123456789123456789 23456
Next Line

The result now looks like this:

123456789123456789123456789123456789123456789123456789123456789123456789123456789123456789
23456
Next Line

Somehow, after 96 characters, the regular expression is interpreting the space as a new line.  Reduce the input one character like this:

123456789123456789123456789123456789123456789123456789123456789123456789123456789123456789 2345
Next Line

Now, I get the expected result with only two lines of data and two multivalued inputs.

My apologies if word wrapping makes this a bit unclear.  I've attached image examples that show the behavior a bit more clearly.

I haven't eliminated the possibility that I'm just using a poor regular expression.  I've tested the data and regular expression on other testers and it seems to work fine outside of Laserfiche cloud.  It even seems to work fine in the On-prem workflow designer.  If there's a better regex, I'm all for it.  If not, is this maybe a bug?