blue-prism-schedule-monitor

[KarthikChandra2]

Greetings All,

We have tested "Function for Blue Prism Schedule Monitor - 1.1.0" in our environment but getting the below logs every time this executable triggers.

https://community.blueprism.com/communities/community-home?CommunityKey=1e516cfe-4d1f-4de9-a9eb-58d15bf38c81

Any help would be great

2022-11-30T12:00:51.1253898Z|INFO|---------------------------
2022-11-30T12:05:48.7294401Z|INFO|Initiating
2022-11-30T12:05:48.7584392Z|INFO|Opening connection to database
2022-11-30T12:05:48.8756103Z|INFO|Database connection opened
2022-11-30T12:05:48.9322559Z|INFO|Querying database for misfired schedules
2022-11-30T12:05:50.9389904Z|INFO|Query executed successfully
2022-11-30T12:05:51.0542937Z|FATAL|STRING_AGG aggregation result exceeded the limit of 8000 bytes. Use LOB types to avoid result truncation.
2022-11-30T12:05:51.0562933Z|INFO|---------------------------
2022-11-30T12:10:48.8829154Z|INFO|Initiating
2022-11-30T12:10:48.9239178Z|INFO|Opening connection to database
2022-11-30T12:10:49.1528510Z|INFO|Database connection opened
2022-11-30T12:10:49.2558508Z|INFO|Querying database for misfired schedules
2022-11-30T12:10:51.6189812Z|INFO|Query executed successfully
2022-11-30T12:10:51.6915024Z|FATAL|STRING_AGG aggregation result exceeded the limit of 8000 bytes. Use LOB types to avoid result truncation.
2022-11-30T12:10:51.6945014Z|INFO|---------------------------

[CharlieKovacs]

Hi Karthik,

That is a bug in the Schedule Monitor that the STRING_AGG function is exceeding the 8,000 character limit in an unhandled way. I think the solution will be to truncate at that limit. I will look into providing an updated version of the Schedule Monitor and report back when I have this solved.

[Prathamesh_]

Hi karthik did you find any solution for this?

[CharlieKovacs]

Hi Karthik,

Version 1.2.0 addresses this issue with the STRING_AGG function running over the 8,000 byte limit.
https://digitalexchange.blueprism.com/dx/entry/9648/solution/blue-prism-schedule-monitor

Let me know if the issue persists.

[yosuke]

Hi Charlie,

We have received the following report related error messages using version 1.2.0 of this tool.
Could you please guide us as to the cause and solution?

2023-03-09T08:15:01.8838897Z|INFO|Initiating
2023-03-09T08:15:01.9128134Z|INFO|Opening connection to database
2023-03-09T08:15:02.2734872Z|INFO|Database connection opened
2023-03-09T08:15:02.3502907Z|INFO|Querying database for misfired schedules
2023-03-09T08:15:02.4342087Z|FATAL|'STRING_AGG' is not a recognized built-in function name.
Incorrect syntax near the keyword 'as'.
2023-03-09T08:15:02.4361990Z|INFO|---------------------------

[CharlieKovacs]

@yosuke - The most likely reason for that error is that the STRING_AGG function is only available in SQL Server 2017 or later.

[LonSwain]

Is that to say the Utility will only run on SQL 2017 or later?  I'm getting the same error but I know we're running 2016.