Work Queues -> Get Report Data not bringing out the correct number of exceptions

[emeka.ozonze]

Our bot has been generating incorrect reports. On detailed study, we noticed that "Work Queues -> Get Report Data" is not getting out the correct number of exceptions. For example, there were 3 exceptions yesterday (23-05-2024), but "Work Queues -> Get Report Data" is outputting 2 exceptions. Start Time and End Time are set to "23/05/2024 00:00:01" and "23/05/2024 23:59:01" respectively. Has anyone experienced this issue? Blue Prism version is 6.10.4.

Any help with resolving this will be highly appreciated.

Many thanks,
Emeka

[Mohamad_Dakkouri · Accepted solution]

Hi @emeka.ozonze 

We had the same issue, and we fixed it via the UTC Time.

Can you try to convert the time provided in UTC ?

For instance if your start date is 24/05/2024 00:00:00 convert it to UTC via Utility Date and Time Manipulation with action Local to UTC.

Do the same for the end date 

And try then to run your get report data with UTC date 🙂

Regards

[Daniel_Sanhueza]

Hi @emeka.ozonze,

Please follow the advice that @Mohamad_Dakkouri, I just wanted to add some useful info that you could find on blue-prism-6-date-and-time-handling 

The following product design principles relates should be considered

• For storage and data transfer, an instant in time is always represented as UTC.
• Within the user interface, dates and times are commonly presented according to the user’s local
  time preferences (as determined by the Operating System or browser).
• Schedule start times are saved based on the local time-zone settings of the device used to
  configure the schedule. Schedules are executed by the server based on the server’s local time.

The "Get Report Data" is expected to receive UTC Date, same applies to "Defer", "Get Exception Items" and some others. If you use "Get Item Data" , the date outputs are also coming in UTC and the approach that @Mohamad_Dakkouri said should be implemented but inversed (UTC to local).

Regards

[emeka.ozonze]

Many thanks @Mohamad_Dakkouri ! This solved it perfectly.

[emeka.ozonze]

Many thanks, @Daniel_Sanhueza , for the additional info. This solved it perfectly.