web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Adding pause capabilit...
Power Automate
Unanswered

Adding pause capability to calculating time

(0) ShareShare
ReportReport
Posted on by 56

Hi all,

I have a simple ticket system using a SharePoint online list.  There is a status column with Pending (default), Working, Closed.
I have a simple calculation that takes the Closed Date (captured when user puts status in Closed) and subtracts the Created date and gives me the total hours worked (just SP calculated column).

Now the user wants to know if we can add a Paused status that will stop the time calculation until the ticket is put back into a Working status and i'm thinking a Flow would better manage this.

 

So for example a ticket is submitted at 8:00 am and goes from Pending to Working until 10:00 am when the technician places it in a Paused status due to waiting on a vendor.  So right now there is 2 hours worked. 

The ticket stays paused until 2 pm when the technician puts it's back into a Working Status until 4 pm when it is placed back into Paused because it is now end of day. 

So that would only add another 2 hours worked for a new running total of 4 hours.

The next day at 8 am the ticket is now Working again until 11 am when it is closed - so the complete total working hours on that ticket should come up to 7 hours.

 

I am unsure about how this might work with a flow - would i just use conditions?  or a pause until condition is met?  Would this make sure that the Flow doesn't try to restart on every change?  Looking for recommendations or ideas 🙂

 

Thanks!

Categories:
I have the same question (0)
  • ScottShearer Profile Picture
    25,270 Most Valuable Professional on at

    @scutiyog 

    I suggest trying a solution using two columns in SharePoint - one for accumulated time(a number column)  and the other for running time ( a date/time column with minutes).

    • When a ticket is put in a status where the clock should be running, the current time is logged in the running time column
    • When the ticket is put in a status where the clock should stop, the current time is compared to the current time.  The difference is added to any accumulated time and stored in the accumulated time column.  At this point you should zero out the current time column.

    Make sense?  If not, please let me know.

     

     

  • scutiyog Profile Picture
    56 on at

    Thanks Scott for idea - I think i get what you are suggesting - let me run with it and see what i come up with and if i have any questions - or a quick success - i'll report back soon!

     

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard