cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
RJF61
Post Patron
Post Patron

Flow with "Random" Issue/Error

I have a Recurrence Flow that collects SharePoint data with dates greater than (gt) RptStartDate and less than (lt) RptEndDate.  Through the Compose, Apply to each, arrays, etc., I am generating HTML tables that groups data by Supervisor and then counts records entered by each Employee.  The summaries are generating correctly for each Supervisor and each lists the appropriate employees.  In general it identifies the appropriate quantity of entries provided by each employee.; however, I experienced errors with 4 of the 13 Supervisor summaries where the count did not calculate the appropriate number of entries for an Employee (these were not the same employee).  In the following data, the count was (13) versus the (18) actual records.  All records are present in SharePoint and they appear to fit the time window gt 08/14/2022 and lt 08/20/2022; however, the summery count is in error.  The other summaries (with errors) were similar in that the majority of the counts were accurate.

 

Summary report data and counts for Supervisor (PJ)...

EmployeeName

SLAMSubmitted

Employee 1

4

Employee 2

4

Employee 3

2

Employee 4

4

Employee 5

3

Employee 6

3

Employee 7

4

Employee 8

13

 

Following are the exported records from SharePoint for the Supervisor (PJ)...

Created By           Created

Employee 18/19/2022 14:54
Employee 18/19/2022 14:56
Employee 18/19/2022 14:57
Employee 18/19/2022 14:58
Employee 28/17/2022 12:13
Employee 28/17/2022 12:15
Employee 28/18/2022 12:09
Employee 28/19/2022 15:05
Employee 38/17/2022 12:06
Employee 38/17/2022 12:16
Employee 48/16/2022 15:28
Employee 48/16/2022 15:30
Employee 48/16/2022 15:33
Employee 48/18/2022 7:34
Employee 58/15/2022 14:36
Employee 58/19/2022 13:09
Employee 58/19/2022 13:14
Employee 68/16/2022 15:41
Employee 68/19/2022 14:54
Employee 68/19/2022 14:58
Employee 78/18/2022 15:38
Employee 78/18/2022 15:39
Employee 78/19/2022 7:27
Employee 78/19/2022 9:07
Employee 88/17/2022 9:06
Employee 88/17/2022 9:11
Employee 88/17/2022 9:16
Employee 88/18/2022 6:13
Employee 88/18/2022 6:17
Employee 88/18/2022 6:18
Employee 88/18/2022 6:22
Employee 88/18/2022 6:27
Employee 88/18/2022 6:30
Employee 88/18/2022 6:36
Employee 88/19/2022 7:34
Employee 88/19/2022 7:36
Employee 88/19/2022 7:42
Employee 88/19/2022 7:44
Employee 88/19/2022 7:46
Employee 88/19/2022 7:50
Employee 88/19/2022 7:52
Employee 88/19/2022 7:54

     

RJF61_0-1661187576007.png

RJF61_1-1661187670389.png

RJF61_2-1661187734011.png

RJF61_3-1661187787227.png

I had thought the issue was possibly relative to UTC and the Created dates; however, I have been unable to identify.  Any suggestions on where to look?

 

Thanks

1 REPLY 1
Koen5
Resolver III
Resolver III

Dear RJF61,

From what you say and show, it seems pretty straightforward ... my first thought would also be to dive deeper into the date syntax/definition. 

Could it be a suggestion to try and trigger certain errors or results on purpose? Manipulate the data in such a way that it will throw an error or will generate a certain type of result.

This may help you find the cause of issues or exclude certain issues for sure.

 

Hope this can help you further,

Happy flowing,

Koen

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Microsoft 365 Conference – December 6-8, 2022

Microsoft 365 Conference – December 6-8, 2022

Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (5,711)