Hr Task Timer 1 4 0

broken image


  1. Timer 1 Hour
  2. Hr Task Timer 1 4 0 25
  3. Hr Task Timer 1 4 00
-->

A small tool program to self time yourself on the popular chat program Paltalk. One exe file only. No installation, just place the program file into a convenient folder. Optionally drag it and pin it to the task bar for quick launch. Quick time set in 1 min. Intervals up to. Generally you run a scheduled task that has a finite run time and then the task exits. I don't understand what sort of task you would have that would start a new instance every hour but never exit. If it is a task that never exits, then you need to build your own timer into the task. That is beyond the scope of the task scheduler. The following takes a few more lines but is clear and understandable. It saves stdout and stderr to separate files, each with a timestamp. The timestamp includes year, month, day, hour, minute, and second, in that order.

Logic Apps helps you create and run automated recurring tasks and processes on a schedule. By creating a logic app workflow that starts with a built-in Recurrence trigger or Sliding Window trigger, which are Schedule-type triggers, you can run tasks immediately, at a later time, or on a recurring interval. You can call services inside and outside Azure, such as HTTP or HTTPS endpoints, post messages to Azure services such as Azure Storage and Azure Service Bus, or get files uploaded to a file share. With the Recurrence trigger, you can also set up complex schedules and advanced recurrences for running tasks. To learn more about the built-in Schedule triggers and actions, see Schedule triggers and Schedule actions.

Tip

You can schedule and run recurring workloads without creating a separate logic app for each scheduled job and running into the limit on workflows per region and subscription. Instead, you can use the logic app pattern that's created by the Azure QuickStart template: Logic Apps job scheduler.

The Logic Apps job scheduler template creates a CreateTimerJob logic app that calls a TimerJob logic app. You can then call the CreateTimerJob logic app as an API by making an HTTP request and passing a schedule as input for the request. Each call to the CreateTimerJob logic app also calls the TimerJob logic app, which creates a new TimerJob instance that continuously runs based on the specified schedule or until meeting a specified limit. That way, you can run as many TimerJob instances as you want without worrying about workflow limits because instances aren't individual logic app workflow definitions or resources.

This list shows some example tasks that you can run with the Schedule built-in triggers:

  • Get internal data, such as run a SQL stored procedure every day.

  • Get external data, such as pull weather reports from NOAA every 15 minutes.

  • Send report data, such as email a summary for all orders greater than a specific amount in the past week.

  • Process data, such as compress today's uploaded images every weekday during off-peak hours.

  • Clean up data, such as delete all tweets older than three months.

  • Archive data, such as push invoices to a backup service at 1:00 AM every day for the next nine months.

You can also use the Schedule built-in actions to pause your workflow before the next action runs, for example:

  • Wait until a weekday to send a status update over email.

  • Delay the workflow until an HTTP call has time to finish before resuming and retrieving the result.

This article describes the capabilities for the Schedule built-in triggers and actions.

Schedule triggers

You can start your logic app workflow by using the Recurrence trigger or Sliding Window trigger, which isn't associated with any specific service or system. These triggers start and run your workflow based on your specified recurrence where you select the interval and frequency, such as the number of seconds, minutes, hours, days, weeks, or months. You can also set the start date and time along with the time zone. Each time that a trigger fires, Logic Apps creates and runs a new workflow instance for your logic app.

Here are the differences between these triggers:

  • Recurrence: Runs your workflow at regular time intervals based on your specified schedule. If the trigger misses recurrences, for example, due to disruptions or disabled workflows, the Recurrence trigger doesn't process the missed recurrences but restarts recurrences with the next scheduled interval.

    If you select Day as the frequency, you can specify the hours of the day and minutes of the hour, for example, every day at 2:30. If you select Week as the frequency, you can also select days of the week, such as Wednesday and Saturday. You can also specify a start date and time along with a time zone for your recurrence schedule.

    Tip

    If a recurrence doesn't specify a specific start date and time, the first recurrence runs immediatelywhen you save or deploy the logic app, despite your trigger's recurrence setup. To avoid this behavior, provide a startdate and time for when you want the first recurrence to run.

    If a recurrence doesn't specify any other advanced scheduling options such as specific times to run future recurrences,those recurrences are based on the last run time. As a result, the start times for those recurrences might drift due tofactors such as latency during storage calls. To make sure that your logic app doesn't miss a recurrence, especially whenthe frequency is in days or longer, try these options:

    • Provide a start date and time for the recurrence plus the specific times when to run subsequent recurrences by using the propertiesnamed At these hours and At these minutes, which are available only for the Day and Week frequencies.

    • Use the Sliding Window trigger, rather than the Recurrence trigger.

    For more information, see Create, schedule, and run recurring tasks and workflows with the Recurrence trigger.

  • Sliding Window: Runs your workflow at regular time intervals that handle data in continuous chunks. If the trigger misses recurrences, for example, due to disruptions or disabled workflows, the Sliding Window trigger goes back and processes the missed recurrences.

    You can specify a start date and time, time zone, and a duration to delay each recurrence in your workflow. This trigger doesn't support advanced schedules, for example, specific hours of the day, minutes of the hour, and days of the week. For more information, see Create, schedule, and run recurring tasks and workflows with the Sliding Window trigger.

Schedule actions

After any action in your logic app workflow, you can use the Delay and Delay Until actions to make your workflow wait before the next action runs.

  • Delay: Wait to run the next action for the specified number of time units, such as seconds, minutes, hours, days, weeks, or months. For more information, see Delay the next action in workflows.

  • Delay until: Wait to run the next action until the specified date and time. For more information, see Delay the next action in workflows.

Timer

Patterns for start date and time

Here are some patterns that show how you can control recurrence with the start date and time, and how the Logic Apps service runs these recurrences:

Start timeRecurrence without scheduleRecurrence with schedule (Recurrence trigger only)
{none}Runs the first workload instantly.

Runs future workloads based on the last run time.

Runs the first workload instantly.

Runs future workloads based on the specified schedule.

Start time in the pastRecurrence trigger: Calculates run times based on the specified start time and discards past run times.

Runs the first workload at the next future run time.

Runs future workloads based on the last run time.

Sliding Window trigger: Calculates run times based on the specified start time and honors past run times.

Runs future workloads based on the specified start time.

For more explanation, see the example following this table.

Runs the first workload no sooner than the start time, based on the schedule calculated from the start time.

Runs future workloads based on the specified schedule.

Note: If you specify a recurrence with a schedule, but don't specify hours or minutes for the schedule, Logic Apps calculates future run times by using the hours or minutes, respectively, from the first run time.

Start time now or in the futureRuns the first workload at the specified start time.

Recurrence trigger: Runs future workloads based on the last run time.

Sliding Window trigger: Runs future workloads based on the specified start time.

Runs the first workload no sooner than the start time, based on the schedule calculated from the start time.

Runs future workloads based on the specified schedule.

Note: If you specify a recurrence with a schedule, but don't specify hours or minutes for the schedule, Logic Apps calculates future run times by using the hours or minutes, respectively, from the first run time.

Example for past start time and recurrence but no schedule

Suppose the current date and time is September 8, 2017 at 1:00 PM. You specify the start date and time as September 7, 2017 at 2:00 PM, which is in the past, and a recurrence that runs every two days.

Start timeCurrent timeRecurrenceSchedule
2017-09-07T14:00:00Z
(2017-09-07 at 2:00 PM)
2017-09-08T13:00:00Z
(2017-09-08 at 1:00 PM)
Every two days{none}

For the Recurrence trigger, the Logic Apps engine calculates run times based on the start time, discards past run times, uses the next future start time for the first run, and calculates future runs based on the last run time.

Here's how this recurrence looks:

Start timeFirst run timeFuture run times
2017-09-07 at 2:00 PM2017-09-09 at 2:00 PM2017-09-11 at 2:00 PM
2017-09-13 at 2:00 PM
2017-09-15 at 2:00 PM
and so on..

So, no matter how far in the past you specify the start time, for example, 2017-09-05 at 2:00 PM or 2017-09-01 at 2:00 PM, your first run always uses the next future start time.

For the Sliding Window trigger, the Logic Apps engine calculates run times based on the start time, honors past run times, uses the start time for the first run, and calculates future runs based on the start time.

Here's how this recurrence looks:

Start timeFirst run timeFuture run times
2017-09-07 at 2:00 PM2017-09-08 at 1:00 PM (Current time)2017-09-09 at 2:00 PM
2017-09-11 at 2:00 PM
2017-09-13 at 2:00 PM
2017-09-15 at 2:00 PM
and so on..

So, no matter how far in the past you specify the start time, for example, 2017-09-05 at 2:00 PM or 2017-09-01 at 2:00 PM, your first run always uses the specified start time.

Recurrence for daylight saving time and standard time

Recurring built-in triggers honor the schedule that you set, including any time zone that you specify. If you don't select a time zone, daylight saving time (DST) might affect when triggers run, for example, shifting the start time one hour forward when DST starts and one hour backward when DST ends. When scheduling jobs, Logic Apps puts the message for processing into the queue and specifies when that message becomes available, based on the UTC time when the last job ran and the UTC time when the next job is scheduled to run.

To avoid this shift so that your logic app runs at your specified start time, make sure that you select a time zone. That way, the UTC time for your logic app also shifts to counter the seasonal time change.

Note

Triggers that start between 2:00 AM - 3:00 AM might have problems because DST changes happen at 2:00 AM, which mightcause the start time to become invalid or ambiguous. If you have multiple logic apps within the same ambiguous interval,they might overlap. For this reason, you might want to avoid start times between 2:00 AM - 3:00 AM.

For example, suppose that you have two logic apps that run daily. One logic app runs at 1:30 AM local time, while the other runs an hour later at 2:30 AM local time. What happens to the starting times for these apps when DST starts and ends?

  • Do the triggers run at all when the time shifts one hour forward?

  • Do the triggers run twice when the time shifts one hour backward?

If these logic apps use the UTC-6:00 Central Time (US & Canada) zone, this simulation shows how the UTC times shifted in 2019 to counter the DST changes, moving one hour backward or forward as necessary so that the apps continued running at the expected local times without skipped or duplicate runs.

  • 03/10/2019: DST starts at 2:00 AM, shifting time one hour forward

    To compensate after DST starts, UTC time shifts one hour backward so that your logic app continues running at the same local time:

    • Logic app #1

      DateTime (local)Time (UTC)Notes
      03/09/20191:30:00 AM7:30:00 AMUTC before the day that DST takes effect.
      03/10/20191:30:00 AM7:30:00 AMUTC is the same because DST hasn't taken effect.
      03/11/20191:30:00 AM6:30:00 AMUTC shifted one hour backward after DST took effect.
    • Logic app #2

      DateTime (local)Time (UTC)Notes
      03/09/20192:30:00 AM8:30:00 AMUTC before the day that DST takes effect.
      03/10/20193:30:00 AM*8:30:00 AMDST is already in effect, so local time has moved one hour forward because the UTC-6:00 time zone changes to UTC-5:00. For more information, see Triggers that start between 2:00 AM - 3:00 AM.
      03/11/20192:30:00 AM7:30:00 AMUTC shifted one hour backward after DST took effect.
  • 11/03/2019: DST ends at 2:00 AM and shifts time one hour backward

    To compensate, UTC time shifts one hour forward so that your logic app continues running at the same local time:

    • Logic app #1

      DateTime (local)Time (UTC)Notes
      11/02/20191:30:00 AM6:30:00 AM
      11/03/20191:30:00 AM6:30:00 AM
      11/04/20191:30:00 AM7:30:00 AM
    • Logic app #2

      DateTime (local)Time (UTC)Notes
      11/02/20192:30:00 AM7:30:00 AM
      11/03/20192:30:00 AM8:30:00 AM
      11/04/20192:30:00 AM8:30:00 AM

Run one time only

If you want to run your logic app only at one time in the future, you can use the Scheduler: Run once jobs template. After you create a new logic app but before opening the Logic Apps Designer, under the Templates section, from the Category list, select Schedule, and then select this template:

Or, if you can start your logic app with the When a HTTP request is received - Request trigger, and pass the start time as a parameter for the trigger. For the first action, use the Delay until - Schedule action, and provide the time for when the next action starts running.

Example recurrences

Here are various example recurrences that you can set up for the triggers that support the options:

TriggerRecurrenceIntervalFrequencyStart timeOn these daysAt these hoursAt these minutesNote
Recurrence,
Sliding Window
Run every 15 minutes (no start date and time)15Minute{none}{unavailable}{none}{none}This schedule starts immediately, then calculates future recurrences based on the last run time.
Recurrence,
Sliding Window
Run every 15 minutes (with start date and time)15MinutestartDateTstartTimeZ{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time, then calculates future recurrences based on the last run time.
Recurrence,
Sliding Window
Run every hour, on the hour (with start date and time)1HourstartDateThh:00:00Z{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time. Future recurrences run every hour at the '00' minute mark, which Logic Apps calculates from the start time.

If the frequency is 'Week' or 'Month', this schedule respectively runs only one day per week or one day per month.

Recurrence,
Sliding Window
Run every hour, every day (no start date and time)1Hour{none}{unavailable}{none}{none}This schedule starts immediately and calculates future recurrences based on the last run time.

If the frequency is 'Week' or 'Month', this schedule respectively runs only one day per week or one day per month.

Recurrence,
Sliding Window
Run every hour, every day (with start date and time)1HourstartDateTstartTimeZ{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time, then calculates future recurrences based on the last run time.

If the frequency is 'Week' or 'Month', this schedule respectively runs only one day per week or one day per month.

Recurrence,
Sliding Window
Run every 15 minutes past the hour, every hour (with start date and time)1HourstartDateT00:15:00Z{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time. Future recurrences run at the '15' minute mark, which Logic Apps calculates from the start time, so at 00:15 AM, 1:15 AM, 2:15 AM, and so on.
RecurrenceRun every 15 minutes past the hour, every hour (no start date and time)1Day{none}{unavailable}0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 2315This schedule runs at 00:15 AM, 1:15 AM, 2:15 AM, and so on. Also, this schedule is equivalent to a frequency of 'Hour' and a start time with '15' minutes.
RecurrenceRun every 15 minutes at the specified minute marks (no start date and time).1Day{none}{unavailable}0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 230, 15, 30, 45This schedule doesn't start until the next specified 15-minute mark.
RecurrenceRun daily at 8 AM plus the minute-mark from when you save your logic app1Day{none}{unavailable}8{none}Without a start date and time, this schedule runs based on the time when you save the logic app (PUT operation).
RecurrenceRun daily at 8:00 AM (with start date and time)1DaystartDateT08:00:00Z{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time. Future occurrences run daily at 8:00 AM.
RecurrenceRun daily at 8:00 AM (no start date and time)1Day{none}{unavailable}800This schedule runs at 8:00 AM every day.
RecurrenceRun daily at 8:00 AM and 4:00 PM1Day{none}{unavailable}8, 160
RecurrenceRun daily at 8:30 AM, 8:45 AM, 4:30 PM, and 4:45 PM1Day{none}{unavailable}8, 1630, 45
RecurrenceRun every Saturday at 5:00 PM (no start date and time)1Week{none}'Saturday'170This schedule runs every Saturday at 5:00 PM.
RecurrenceRun every Saturday at 5:00 PM (with start date and time)1WeekstartDateT17:00:00Z'Saturday'{none}{none}This schedule doesn't start any sooner than the specified start date and time, in this case, September 9, 2017 at 5:00 PM. Future recurrences run every Saturday at 5:00 PM.
RecurrenceRun every Tuesday, Thursday at 5 PM plus the minute-mark from when you save your logic app1Week{none}'Tuesday', 'Thursday'17{none}
RecurrenceRun every hour during working hours.1Week{none}Select all days except Saturday and Sunday.Select the hours of the day that you want.Select any minutes of the hour that you want.For example, if your working hours are 8:00 AM to 5:00 PM, then select '8, 9, 10, 11, 12, 13, 14, 15, 16, 17' as the hours of the day plus '0' as the minutes of the hour.
RecurrenceRun once every day on weekends1Week{none}'Saturday', 'Sunday'Select the hours of the day that you want.Select any minutes of the hour as appropriate.This schedule runs every Saturday and Sunday at the specified schedule.
RecurrenceRun every 15 minutes biweekly on Mondays only2Week{none}'Monday'0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 230, 15, 30, 45This schedule runs every other Monday at every 15-minute mark.
RecurrenceRun every month1MonthstartDateTstartTimeZ{unavailable}{unavailable}{unavailable}This schedule doesn't start any sooner than the specified start date and time and calculates future recurrences on the start date and time. If you don't specify a start date and time, this schedule uses the creation date and time.
RecurrenceRun every hour for one day per month1Month{see note}{unavailable}0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23{see note}If you don't specify a start date and time, this schedule uses the creation date and time. To control the minutes for the recurrence schedule, specify the minutes of the hour, a start time, or use the creation time. For example, if the start time or creation time is 8:25 AM, this schedule runs at 8:25 AM, 9:25 AM, 10:25 AM, and so on.

Next steps

What do we mean by best? These are the top-rated free time tracking solutions in our directory.

How long will this task take? What's the level of effort for this activity?

If you aren't using time tracking software, it's hard to accurately answer those questions. And estimating incorrectly can cost you valuable time and money. Luckily, you don't have to break the bank to find a solution.

If you have a small team, are on a tight budget, and are willing to compromise on some premium features, then a free or freemium time tracking product may be right for you. (Freemium products are free versions of paid software that offer limited functionality, users seats, or both.)

In this article, we're highlighting eight top-rated* free time tracking software options in Capterra's directory, and each solution's cost to upgrade.

Use this list to determine 1) if free software is the right solution for your organization, and 2) which free system is best for your needs.

What does 'top-rated' mean? Each of the eight tools included in this piece have an above-average overall user rating compared to other products in the category and have a high number of reviews from project managers, specifically. You can find our full methodology here.

This article looks at eight highly rated free time-tracking software options. See the full list of free time-tracking software solutions here.

Products are presented alphabetically.

Jump to:


  • Avaza

  • Clockify

  • Freedcamp

  • Harvest

  • Hubstaff

  • MeisterTask

  • TimeCamp

  • Toggl

Minute

Patterns for start date and time

Here are some patterns that show how you can control recurrence with the start date and time, and how the Logic Apps service runs these recurrences:

Start timeRecurrence without scheduleRecurrence with schedule (Recurrence trigger only)
{none}Runs the first workload instantly.

Runs future workloads based on the last run time.

Runs the first workload instantly.

Runs future workloads based on the specified schedule.

Start time in the pastRecurrence trigger: Calculates run times based on the specified start time and discards past run times.

Runs the first workload at the next future run time.

Runs future workloads based on the last run time.

Sliding Window trigger: Calculates run times based on the specified start time and honors past run times.

Runs future workloads based on the specified start time.

For more explanation, see the example following this table.

Runs the first workload no sooner than the start time, based on the schedule calculated from the start time.

Runs future workloads based on the specified schedule.

Note: If you specify a recurrence with a schedule, but don't specify hours or minutes for the schedule, Logic Apps calculates future run times by using the hours or minutes, respectively, from the first run time.

Start time now or in the futureRuns the first workload at the specified start time.

Recurrence trigger: Runs future workloads based on the last run time.

Sliding Window trigger: Runs future workloads based on the specified start time.

Runs the first workload no sooner than the start time, based on the schedule calculated from the start time.

Runs future workloads based on the specified schedule.

Note: If you specify a recurrence with a schedule, but don't specify hours or minutes for the schedule, Logic Apps calculates future run times by using the hours or minutes, respectively, from the first run time.

Example for past start time and recurrence but no schedule

Suppose the current date and time is September 8, 2017 at 1:00 PM. You specify the start date and time as September 7, 2017 at 2:00 PM, which is in the past, and a recurrence that runs every two days.

Start timeCurrent timeRecurrenceSchedule
2017-09-07T14:00:00Z
(2017-09-07 at 2:00 PM)
2017-09-08T13:00:00Z
(2017-09-08 at 1:00 PM)
Every two days{none}

For the Recurrence trigger, the Logic Apps engine calculates run times based on the start time, discards past run times, uses the next future start time for the first run, and calculates future runs based on the last run time.

Here's how this recurrence looks:

Start timeFirst run timeFuture run times
2017-09-07 at 2:00 PM2017-09-09 at 2:00 PM2017-09-11 at 2:00 PM
2017-09-13 at 2:00 PM
2017-09-15 at 2:00 PM
and so on..

So, no matter how far in the past you specify the start time, for example, 2017-09-05 at 2:00 PM or 2017-09-01 at 2:00 PM, your first run always uses the next future start time.

For the Sliding Window trigger, the Logic Apps engine calculates run times based on the start time, honors past run times, uses the start time for the first run, and calculates future runs based on the start time.

Here's how this recurrence looks:

Start timeFirst run timeFuture run times
2017-09-07 at 2:00 PM2017-09-08 at 1:00 PM (Current time)2017-09-09 at 2:00 PM
2017-09-11 at 2:00 PM
2017-09-13 at 2:00 PM
2017-09-15 at 2:00 PM
and so on..

So, no matter how far in the past you specify the start time, for example, 2017-09-05 at 2:00 PM or 2017-09-01 at 2:00 PM, your first run always uses the specified start time.

Recurrence for daylight saving time and standard time

Recurring built-in triggers honor the schedule that you set, including any time zone that you specify. If you don't select a time zone, daylight saving time (DST) might affect when triggers run, for example, shifting the start time one hour forward when DST starts and one hour backward when DST ends. When scheduling jobs, Logic Apps puts the message for processing into the queue and specifies when that message becomes available, based on the UTC time when the last job ran and the UTC time when the next job is scheduled to run.

To avoid this shift so that your logic app runs at your specified start time, make sure that you select a time zone. That way, the UTC time for your logic app also shifts to counter the seasonal time change.

Note

Triggers that start between 2:00 AM - 3:00 AM might have problems because DST changes happen at 2:00 AM, which mightcause the start time to become invalid or ambiguous. If you have multiple logic apps within the same ambiguous interval,they might overlap. For this reason, you might want to avoid start times between 2:00 AM - 3:00 AM.

For example, suppose that you have two logic apps that run daily. One logic app runs at 1:30 AM local time, while the other runs an hour later at 2:30 AM local time. What happens to the starting times for these apps when DST starts and ends?

  • Do the triggers run at all when the time shifts one hour forward?

  • Do the triggers run twice when the time shifts one hour backward?

If these logic apps use the UTC-6:00 Central Time (US & Canada) zone, this simulation shows how the UTC times shifted in 2019 to counter the DST changes, moving one hour backward or forward as necessary so that the apps continued running at the expected local times without skipped or duplicate runs.

  • 03/10/2019: DST starts at 2:00 AM, shifting time one hour forward

    To compensate after DST starts, UTC time shifts one hour backward so that your logic app continues running at the same local time:

    • Logic app #1

      DateTime (local)Time (UTC)Notes
      03/09/20191:30:00 AM7:30:00 AMUTC before the day that DST takes effect.
      03/10/20191:30:00 AM7:30:00 AMUTC is the same because DST hasn't taken effect.
      03/11/20191:30:00 AM6:30:00 AMUTC shifted one hour backward after DST took effect.
    • Logic app #2

      DateTime (local)Time (UTC)Notes
      03/09/20192:30:00 AM8:30:00 AMUTC before the day that DST takes effect.
      03/10/20193:30:00 AM*8:30:00 AMDST is already in effect, so local time has moved one hour forward because the UTC-6:00 time zone changes to UTC-5:00. For more information, see Triggers that start between 2:00 AM - 3:00 AM.
      03/11/20192:30:00 AM7:30:00 AMUTC shifted one hour backward after DST took effect.
  • 11/03/2019: DST ends at 2:00 AM and shifts time one hour backward

    To compensate, UTC time shifts one hour forward so that your logic app continues running at the same local time:

    • Logic app #1

      DateTime (local)Time (UTC)Notes
      11/02/20191:30:00 AM6:30:00 AM
      11/03/20191:30:00 AM6:30:00 AM
      11/04/20191:30:00 AM7:30:00 AM
    • Logic app #2

      DateTime (local)Time (UTC)Notes
      11/02/20192:30:00 AM7:30:00 AM
      11/03/20192:30:00 AM8:30:00 AM
      11/04/20192:30:00 AM8:30:00 AM

Run one time only

If you want to run your logic app only at one time in the future, you can use the Scheduler: Run once jobs template. After you create a new logic app but before opening the Logic Apps Designer, under the Templates section, from the Category list, select Schedule, and then select this template:

Or, if you can start your logic app with the When a HTTP request is received - Request trigger, and pass the start time as a parameter for the trigger. For the first action, use the Delay until - Schedule action, and provide the time for when the next action starts running.

Example recurrences

Here are various example recurrences that you can set up for the triggers that support the options:

TriggerRecurrenceIntervalFrequencyStart timeOn these daysAt these hoursAt these minutesNote
Recurrence,
Sliding Window
Run every 15 minutes (no start date and time)15Minute{none}{unavailable}{none}{none}This schedule starts immediately, then calculates future recurrences based on the last run time.
Recurrence,
Sliding Window
Run every 15 minutes (with start date and time)15MinutestartDateTstartTimeZ{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time, then calculates future recurrences based on the last run time.
Recurrence,
Sliding Window
Run every hour, on the hour (with start date and time)1HourstartDateThh:00:00Z{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time. Future recurrences run every hour at the '00' minute mark, which Logic Apps calculates from the start time.

If the frequency is 'Week' or 'Month', this schedule respectively runs only one day per week or one day per month.

Recurrence,
Sliding Window
Run every hour, every day (no start date and time)1Hour{none}{unavailable}{none}{none}This schedule starts immediately and calculates future recurrences based on the last run time.

If the frequency is 'Week' or 'Month', this schedule respectively runs only one day per week or one day per month.

Recurrence,
Sliding Window
Run every hour, every day (with start date and time)1HourstartDateTstartTimeZ{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time, then calculates future recurrences based on the last run time.

If the frequency is 'Week' or 'Month', this schedule respectively runs only one day per week or one day per month.

Recurrence,
Sliding Window
Run every 15 minutes past the hour, every hour (with start date and time)1HourstartDateT00:15:00Z{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time. Future recurrences run at the '15' minute mark, which Logic Apps calculates from the start time, so at 00:15 AM, 1:15 AM, 2:15 AM, and so on.
RecurrenceRun every 15 minutes past the hour, every hour (no start date and time)1Day{none}{unavailable}0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 2315This schedule runs at 00:15 AM, 1:15 AM, 2:15 AM, and so on. Also, this schedule is equivalent to a frequency of 'Hour' and a start time with '15' minutes.
RecurrenceRun every 15 minutes at the specified minute marks (no start date and time).1Day{none}{unavailable}0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 230, 15, 30, 45This schedule doesn't start until the next specified 15-minute mark.
RecurrenceRun daily at 8 AM plus the minute-mark from when you save your logic app1Day{none}{unavailable}8{none}Without a start date and time, this schedule runs based on the time when you save the logic app (PUT operation).
RecurrenceRun daily at 8:00 AM (with start date and time)1DaystartDateT08:00:00Z{unavailable}{none}{none}This schedule doesn't start any sooner than the specified start date and time. Future occurrences run daily at 8:00 AM.
RecurrenceRun daily at 8:00 AM (no start date and time)1Day{none}{unavailable}800This schedule runs at 8:00 AM every day.
RecurrenceRun daily at 8:00 AM and 4:00 PM1Day{none}{unavailable}8, 160
RecurrenceRun daily at 8:30 AM, 8:45 AM, 4:30 PM, and 4:45 PM1Day{none}{unavailable}8, 1630, 45
RecurrenceRun every Saturday at 5:00 PM (no start date and time)1Week{none}'Saturday'170This schedule runs every Saturday at 5:00 PM.
RecurrenceRun every Saturday at 5:00 PM (with start date and time)1WeekstartDateT17:00:00Z'Saturday'{none}{none}This schedule doesn't start any sooner than the specified start date and time, in this case, September 9, 2017 at 5:00 PM. Future recurrences run every Saturday at 5:00 PM.
RecurrenceRun every Tuesday, Thursday at 5 PM plus the minute-mark from when you save your logic app1Week{none}'Tuesday', 'Thursday'17{none}
RecurrenceRun every hour during working hours.1Week{none}Select all days except Saturday and Sunday.Select the hours of the day that you want.Select any minutes of the hour that you want.For example, if your working hours are 8:00 AM to 5:00 PM, then select '8, 9, 10, 11, 12, 13, 14, 15, 16, 17' as the hours of the day plus '0' as the minutes of the hour.
RecurrenceRun once every day on weekends1Week{none}'Saturday', 'Sunday'Select the hours of the day that you want.Select any minutes of the hour as appropriate.This schedule runs every Saturday and Sunday at the specified schedule.
RecurrenceRun every 15 minutes biweekly on Mondays only2Week{none}'Monday'0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 230, 15, 30, 45This schedule runs every other Monday at every 15-minute mark.
RecurrenceRun every month1MonthstartDateTstartTimeZ{unavailable}{unavailable}{unavailable}This schedule doesn't start any sooner than the specified start date and time and calculates future recurrences on the start date and time. If you don't specify a start date and time, this schedule uses the creation date and time.
RecurrenceRun every hour for one day per month1Month{see note}{unavailable}0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23{see note}If you don't specify a start date and time, this schedule uses the creation date and time. To control the minutes for the recurrence schedule, specify the minutes of the hour, a start time, or use the creation time. For example, if the start time or creation time is 8:25 AM, this schedule runs at 8:25 AM, 9:25 AM, 10:25 AM, and so on.

Next steps

What do we mean by best? These are the top-rated free time tracking solutions in our directory.

How long will this task take? What's the level of effort for this activity?

If you aren't using time tracking software, it's hard to accurately answer those questions. And estimating incorrectly can cost you valuable time and money. Luckily, you don't have to break the bank to find a solution.

If you have a small team, are on a tight budget, and are willing to compromise on some premium features, then a free or freemium time tracking product may be right for you. (Freemium products are free versions of paid software that offer limited functionality, users seats, or both.)

In this article, we're highlighting eight top-rated* free time tracking software options in Capterra's directory, and each solution's cost to upgrade.

Use this list to determine 1) if free software is the right solution for your organization, and 2) which free system is best for your needs.

What does 'top-rated' mean? Each of the eight tools included in this piece have an above-average overall user rating compared to other products in the category and have a high number of reviews from project managers, specifically. You can find our full methodology here.

This article looks at eight highly rated free time-tracking software options. See the full list of free time-tracking software solutions here.

Products are presented alphabetically.

Jump to:


  • Avaza

  • Clockify

  • Freedcamp

  • Harvest

  • Hubstaff

  • MeisterTask

  • TimeCamp

  • Toggl

8 top-rated free time tracking software solutions for project managers

1. Avaza

Avaza is a cloud-based project management (PM) solution that offers time tracking alongside capabilities such as task management and resource management. Key time tracking features include a stopwatch timer, the ability to set flexible rates (e.g., per project, category, or user), differentiation between billable and non-billable hours, timesheet management, and invoicing for time logged on projects. If you are looking for products with similar features, these Avaza alternatives are a great place to start.

Avaza's free plan includes access for one timesheet/expense user (among other user roles) as well as five active projects (unlimited archived projects), 10 customers, five invoices per month, 100 MB of storage, and email and chat support alongside an online knowledge base.

Paid plans include access for additional users/roles, additional active projects, unlimited customers, a higher volume of invoices per month, more storage, and priority support.

Pros Cons
Reviewers praise Avaza's customer support and services (online knowledge base and video tutorials).Reviewers note that Avaza's social collaboration features aren't as robust as other offerings.

Cost to upgrade: When billed monthly—$9.95 per month, (Startup), $19.95 per month (Basic), $39.95 per month (Business).

Integrations:Avaza offers pre-built integrations with over 500 tools, including several other PM and productivity solutions (e.g., Trello, Slack).

Mobile apps:iOS, Android

Highly rated by: In the past year, 87% of Avaza's user reviews on Capterra came from individuals at small businesses. The largest number of reviews were from users in marketing and advertising, and the IT services industry.

Viewing a timesheet in Avaza (Source)

2. Clockify

Clockify is a time tracking solution designed for teams that can be deployed in the cloud or installed on Mac, Windows, or Linux OS. Key features include a stopwatch timer, the ability to set flexible rates (e.g., per project, category, or user), differentiate between billable and non-billable hours, and view user timesheets, in addition to reporting and analytics (track profitability and project progress). Interested in software solutions with similar features? These Clockify alternatives could be what you are looking for.

Clockify's free plan includes unlimited core functionality as well as unlimited users, unlimited projects, email support, and access to their online knowledge base.

Paid plans offer additional functionality such as branded reports, project templates, targets and reminders, and dedicated support.

Pros Cons
Reviewers praise Clockify's simplicity and intuitive UI, stating that it's very straightforward and easy to use.Reviewers note that Clockify doesn't include idle detection, which means they can forget to stop the timer, resulting in inaccurate timesheets.

Cost to upgrade: When billed monthly—$9.99 per month (Plus), $29.99 per month (Premium), $450 per month (Server). Paid plans are sold on a flat price for the workspace, not per user.

Integrations:Clockify offers over 50 pre-built integrations with other web apps, including several PM products (e.g., Trello, Asana, Monday.com, Basecamp).

Mobile apps:iOS, Android

Highly rated by: In the past year, 86% of Clockify's user reviews on Capterra came from individuals at small businesses. The largest number of reviews were from users in computer software, IT services, and the marketing and advertising industry.

Stopwatch timer in Clockify (Source)

3. Freedcamp

Freedcamp is a collaborative work management solution that can be deployed in the cloud or installed on Mac or Windows OS. It offers time tracking alongside other capabilities such as task management, bug tracking, and CRM. Key time tracking features include the ability to track time against different tasks and bill clients for time logged on projects. If you are interested in comparing software solutions with similar features, these Freedcamp alternatives are a great place to start.

Freedcamp's free plan includes access for unlimited users, tasks, project workspaces, and storage, as well as standard support.

Paid plans include premium support and additional functionality such as reporting and analytics, CRM, and invoicing.

Pros Cons
Reviewers praise how customizable Freedcamp is, stating that it's easy to turn modules on and off according to their needs.Several reviewers cite issues with Freedcamp's mobile applications.

Cost to upgrade: When billed monthly—$2.49 per user, per month (Minimalist), $4.99 per user, per month (Freelancer), $8.99 per user, per month (Business), $16.99 per user, per month (Enterprise). Discounts available with an annual subscription.

Integrations:Freedcamp offers over 1,500 integrations through Zapier to various products including Slack, G-suite, and PM tools such as Smartsheet and Monday.com.

Mobile apps:iOS, Android

Highly rated by: In the last year, 88% of Freedcamp's reviews on Capterra came from individuals at small businesses. The largest number of reviews were from users in the marketing and advertising, IT services, and computer software industries.

Managing system in Freedcamp (Source)

4. Harvest

Harvest is a cloud-based time tracking tool designed for teams. Key features include a stopwatch timer, user timesheets, the ability to set flexible rates (e.g., per project, category, or user), differentiation between billable and non-billable hours, invoicing, dashboards for monitoring project progress, and reporting and analytics (e.g., resource capacity and profitability). Want to explore products with similar features? These Harvest alternatives are a good place to begin.

Harvest's free plan includes one user, two projects, all core functionality, phone/email support, and an online help center.

Paid plans include more users and unlimited projects.

Pros Cons
Reviewers note that Harvest is easy to use and integrates with a variety of other business software solutions (e.g., accounting systems, payment processors, PM tools, etc.)Several reviewers say that Harvest's cost is a downside.(NOTE: At $12 per user per month, this is the most expensive free-to-paid upgrade on our list.)

Cost to upgrade: When billed monthly—$12 per person, per month (Solo and Team)

Integrations:Harvest offers hundreds of pre-built integrations with various tools including several PM solutions (e.g., Asana, Basecamp, Smartsheet, Teamwork Projects, Trello).

Timer 1 Hour

Mobile apps:iOS, Android

Highly rated by: In the last year, 86% of Harvest's reviews on Capterra came from individuals at small businesses. The largest number of reviews were from users in the marketing and advertising, design, and computer software industries.

Team overview in Harvest (Source)

5. Hubstaff

Hubstaff is an employee monitoring and time tracking solution that can be deployed in the cloud or installed on Mac or Windows OS. Key time tracking features include a stopwatch timer, user timesheets, idle/inactivity detection, ability to assign pay rates for users, and automatic time tracking via GPS and geofencing. Interested in software solutions with similar features? These Hubstaff alternatives could be what you are looking for.

Hubstaff's free plan includes access for one user, time tracking, activity levels (i.e., tracking activity rates based on mouse and keyboard use), random screen captures, limited payments, email support, and an online help center.

Paid plans include integrations, 24-hour support, and additional functionality such as mobile GPS tracking, payroll, and client and/or project budgets.

Pros Cons
Several reviewers praise the accuracy of Hubstaff's time tracking due to the product's idle/inactivity warnings.Preferences for a product's user interface (UI) are subjective, but it's a factor that can make or break and implementation. Several users state that Hubstaff's UI is a pro and several state that it's a con. The takeaway? If Hubstaff checks all your other boxes, involve end-users in the demo and get their opinions on the UI before you invest your time (and/or your money) in this tool.

Cost to upgrade: When billed monthly—$5 per user, per month (Basic), $10 per user, per month (Premium), $20 per user, per month (Enterprise). Macx mediatrans 6 8 (20200106).

Integrations:Hubstaff offers hundreds of pre-built integrations with various business software, including many PM solutions (e.g., JIRA, LiquidPlanner, Mavenlink, Redbooth, Trello).

Mobile apps:iOS, Android

Highly rated by: In the last year, 96% of Hubstaff's reviews on Capterra came from individuals at small businesses. The largest number of reviews were from users in the marketing and advertising, computer software, and IT services industries.

User report in Hubstaff (Source)

6. MeisterTask

MeisterTask is a visual work management solution that can be deployed in the cloud or installed on Mac or Windows OS. It offers time tracking alongside other capabilities such as task management and collaboration. Key time tracking features include a stopwatch timer, the ability to log time against tasks, and time reports (e.g., time logged per user, task, or project). If you want to explore software solutions with comparable features, these MeisterTask alternatives are a great place to start.

MeisterTask's free plan includes unlimited users, tasks, time tracking, and storage, as well as limited integrations, email support, and online help documentation.

Paid plans include priority support, unlimited integrations, backups, and functionality such as reports, calendar view, and user roles/permissions.

Pros Cons
Reviewers praise the product's simplicity and say it's easy for new users to get up to speed.Several reviewers note that MeisterTask's free offering is limited, particularly when it comes to workflow automation (i.e., setting recurring tasks).

Cost to upgrade: When paid annually— $8.25 per user, per month (Pro), $20.75 per user, per month (Business).

Integrations:MeisterTask offers several pre-built integrations with various business software solutions, including Slack and Microsoft Teams. Additionally, there are over 1,000 integrations available through Zapier, including PM solutions such as Asana, JIRA, and Trello.

Mobile apps:iOS, Android

Highly rated by: In the past year, 77% of MeisterTask's reviews on Capterra came from individuals at small businesses. The largest number of reviews were from users in the computer software, IT services, and marketing and advertising industries.

Time tracking dashboard in MeisterTask (Source)

7. TimeCamp

TimeCamp is a cloud-based time tracking tool designed for freelancers and teams. Key features include a stopwatch timer, graphical timesheets, the ability to set flexible rates (e.g., per project, category, or user), differentiation between billable and non-billable hours, invoicing, reporting and analytics, and employee monitoring. Looking for products with comparable features? These TimeCamp alternatives are a wonderful place to start.

TimeCamp's free plan includes access for one user, customer support (e.g., chat, online consultations, and a knowledge base), as well as basic time tracking features (e.g., stopwatch timer and graphical timesheets).

Paid plans offer integrations as well as more advanced features including billable time, project costs and budgeting, invoicing, reporting, and employee monitoring.

Pros Cons
Reviewers note that TimeCamp is intuitive and easy to use.Several reviewers cite issues with TimeCamp's reporting feature, wishing it was more flexible or easier to use (i.e., describing it as 'clunky' or noting that it's hard to print reports).

Cost to upgrade: When billed monthly—$7 per user, per month (Basic), $10 per user, per month (Pro). Contact the vendor for enterprise pricing for teams with more than 100 users.

Integrations:TimeCamp offers dozens of pre-built integrations with PM tools including Active Collab, Click Up, Pivotal Tracker, and Target Process.

Hr Task Timer 1 4 0 25

Mobile apps:iOS, Android

Highly rated by: In the past year, 62% of TimeCamp's reviews on Capterra came from individuals at small businesses, 14% from medium, and 24% from large. The largest number of reviews were from users in IT services, computer software, and marketing and advertising.

Graphical timesheet in TimeCamp (Source)

8. Toggl

Toggl is a time tracking solution designed for freelancers and teams that can be deployed in the cloud or installed on Mac or Windows OS. Key features include a stopwatch timer, idle detection, the ability to set flexible rates (e.g., per project, category, or user), differentiation between billable and non-billable hours, reporting and analytics, and employee monitoring. If you want to have a look at software solutions with similar features, these Toggl alternatives are a great starting point.

Toggl's free plan includes access for up to five users, several integrations, and core features such as time tracking, user dashboards, and basic reports.

Paid plans include more integrations and advanced features such as time audits, ability to set billable rates, task management, and project time estimates.

Hr Task Timer 1 4 00

Pros Cons
Reviewers praise Toggl's integrations and the ease with which they can connect the time tracker to other business software.Several reviewers say that Toggl's price is a downside. NOTE: At $10 per user per month, this is the second most expensive free-to-paid upgrade on our list.

Cost to upgrade: When billed monthly—$10 per user, per month (Starter), $20 per user, per month (Premium). Contact the vendor for enterprise pricing.

Integrations:Toggl offers pre-built integrations with over 100 tools, including several PM solutions such as Asana, Basecamp, Pivotal Tracker, Podio, and Redbooth.

Mobile apps:iOS, Android

Highly rated by: In the past year, 84% of Toggl's reviews on Capterra came from individuals at small businesses. The largest number of reviews were from users in the marketing and advertising, computer software, and IT services industries.

Summary time report in Toggl (Source)

Want more?

To be included in this update, products had to meet our review minimum and have an above-average overall user rating compared to other products in the category (see our methodology section below). Additionally, products had to have a high number of reviews from project managers.

However, if you're not concerned with your time tracking tool being reviewed by your peers, the following products met our review and rating minimums for this article, but not the job title requirement:

  • AND CO (248 reviews, 4.9/5 stars)
  • My Hours (21 reviews, 4.8/5 stars)
  • Paymo (64 reviews, 4.5/5 stars)

Additionally, you can visit our time tracking directory and filter the list to show only products that meet various criteria (such as key features needed or number of users).

Want an affordable solution, but aren't sure these products fit your needs? Check out our ranking of the Top 20 Most Affordable PM solutions.

Methodology

This article was updated Aug. 2, 2019. Products considered for this article had to:

  • Offer a free, stand-alone version of the software (not a trial version of the software where you must purchase a product after a limited amount of time).
  • Meet our time tracking market definition.

This definition states that 'Time tracking software helps individuals, teams, and organizations across industries keep track of employee time spent on work efforts, i.e., the time spent on tasks/projects, job sites, shift work, client work, etc. These tools provide insight into level of effort, profitability, and employee habits ultimately helping improve user productivity as well as workload and job planning.'

Software that met the market definition also needed a minimum of 20 user-submitted reviews published between June 30, 2018 – June 30, 2019, and have an above-average overall user rating compared to other products in the category.

  • 'Top' free tools were rated at least 4.5/5 stars overall by users.

Lastly, our time tracking directory lists a variety of time tracking tools that reflect the multifaceted needs of buyers, i.e., tracking time for HR/payroll, construction, project management, legal etc. As such, to identify the best tools for project managers, we analyzed our reviews and chose tools that had a high number of reviews from project managers specifically.

Note: The content in this piece that provides opinions and points of view expressed by users does not represent the views of Capterra.

Looking for Project Management software? Check out Capterra's list of the best Project Management software solutions.





broken image