Cloud Rule Log Format

[edmarks]

I’m working with a cloud rule that I’m debugging via log extraction of “log.info” type commands. The following is a snippet I’ve received from Expert Services and wondering if anyone has seen this very bizarre format and know of a way to get this into something usable. Currently it’s grouped by “log.info” line with multiple rows for each entry breaking out the row data on separate lines. Definitely not a more typical chronological type log.

->logs from line log.info("getEmail: firstName: " + firstName);
Mar 6, 2024 @ 15:14:27.156Row: 1, Column: 2:
Row: 1, Column: 3:
getEmail: firstName: quinnRow: 1, Column: 4:
Row: 2, Column: 1:
Mar 6, 2024 @ 15:13:29.961Row: 2, Column: 2:
Row: 2, Column: 3:
getEmail: firstName: AlokRow: 2, Column: 4:

->logs from line log.info("getEmail: middleName: " + middleName);
Mar 6, 2024 @ 15:14:27.157Row: 1, Column: 2:
Row: 1, Column: 3:
getEmail: middleName: nRow: 1, Column: 4:
Row: 2, Column: 1:
Mar 6, 2024 @ 15:13:29.961Row: 2, Column: 2:
Row: 2, Column: 3:
getEmail: middleName: nRow: 2, Column: 4:

[tyler_stevens]

Hey @edmarks - the formatting with Row/Column entries is caused by copying and pasting the log entries from our internal logging system into an encoded document, like a Word doc. Have the Expert Services architect copy the log messages into a text editor instead, such as Sublime or Notepad++, and then send them over. It will remove all of the Row/Column entries and should help make this more readable.