+ Add Question

Issue with Repetitive Tasks

I am seeing an issue which I need to confirm if it is an existing behaviour. It is very irritating and did not find a solution by searching previous posts. Here is it:

1. I have a repetitive task called 'Update Something' to recur 'every day'
2. It appeared in the 'Today' section yesterday and for some reason I could not complete it.
3. Today morning, it appeared in 'Yesterday' section and as I completed the task today, I marked it to done.
4. What I was expecting was the task to get deleted (strike-off) from 'Yesterday' and appear in 'Today'. It got removed from 'Yesterday' but it did not appear in 'Today'.
5. I completed yesterday's recurrence and today's recurrence is vanished. However, I can see the task for tomorrow.

Am I missing something here?

All responses

Clyde Romo  staff
Replied on Mar 25, 2014 - 12:46 UTC

Hi Harsha,

I did some testing and here's what I found out. If you use "ev day" or "every day" as a due date entry, it should show up everyday and move on to the next day if you have already checked it off for the current day.

With that said, I need some more info for you to be able to help you out further. Please let me know in which platform the problem occurs.

[ ] iOS
[ ] Android (which version)

[ ] Chrome
[ ] Firefox
[ ] IE

[ ] Mac App
[ ] Windows App



Harsha Bharadwaj
Replied on Mar 25, 2014 - 13:44 UTC

Hi Clyde,

The issue is seen in all platforms, so it must be something related to core functionality.

Also note that there is no issue in task moving to next day when today's recurrence is completed.

Its with the completion of yesterday's recurrence today (completion of a carry over task). In this case, today's recurrence vanishes and only tomorrow's is shown. Date of completion is taken not the date of recurrence.

Clyde Romo  staff
Replied on Mar 25, 2014 - 13:52 UTC

Hi Harsha,

With further testing, I was able to confirm that this is indeed the expected behaviour. Sorry for the confusion. If you have an everyday task that's overdue, once completed it should show up tomorrow and not due on todays date.



Harsha Bharadwaj
Replied on Mar 25, 2014 - 16:51 UTC

Oh, this is not what I expected. Please help me on how to handle this real life scenario.

Say, I have a task 'Update Daily Journal' to be done everyday. If I complete updating yesterday's update today, and if the task to update today is vanished, how to keep track of the lost updates? The recurrence for the original day must be completed not for the day of update.

I just took the premium membership coming from RTM and that was very obviously handled there. This looks as surprise to me.

Clyde Romo  staff
Replied on Mar 25, 2014 - 17:32 UTC

Hi Harsha,

A workaround would be to mark it off after you have completed yesterday and today's task. I understand your particular use case and will let them know about it. I believe it's designed this way to prevent multiple overdue tasks in case you miss to complete it the for days.



Laura H
Replied on Mar 25, 2014 - 21:11 UTC

Many systems make a designation here between tasks that recur EVERY x Days and tasks that recur AFTER x Days.

So, if I want to journal EVERY DAY I would set the recurrence to EVERY 1 Day. In this case, it would create the task every day. Even if yesterdays was still marked undone, I would see the task today, and yesterdays appear as overdue.

If I want to water my plants AFTER 4 days, then the task would appear on the appropriate day, continue to show up as overdue until I complete it, then regenerate four days from when I marked it complete.

I would love to see ToDoist support BOTH kinds of recurring tasks.

Joey  premium
Replied on Mar 25, 2014 - 21:27 UTC

This is a very distracting bug to workflow. And it's a big problem for me too -- as I'm sure the staff has already heard. It will remain a problem for other customers because it's just simply not proper behavior.

Harsha is correct -- the task should show up TODAY not tomorrow. The task is based on DUE DATE, which was yesterday. When marked complete, as a daily task, the next occurrence for the item (DueDate:Yesterday plus 1 day) is TODAY.

This is an important overlooked logic flaw that should be corrected ASAP. It's not, as another staff person has stated, simply a philosophy issue. This is a bug.

Harsha Bharadwaj
Replied on Mar 26, 2014 - 05:54 UTC

Hi Clyde,

Can you provide an estimate on when will this bug be fixed? This is a very important factor to decide whether to continue with Todoist. If it takes time, I would be happy to return back when it is fixed. You can process my refund.

David Trey  staff
Replied on Mar 26, 2014 - 12:11 UTC


This is not a bug. If you set a task to "make a phonecall" and won't reach this person for 3 days, when you do reach them on day 4, you will not call them 4 times and check off each instance of the "make a phonecall" task. If the task is "take out the trash" and you won't do it for 2 days, you also won't take the trash on day 3 in parts, 3 times ;-)

That said, we've implemented this to avoid having to "click through" a missed task multiple time while the task wasn't necessarily completed for the past days because it couldn't be. We understand that in some situations, some tasks actually do require dealing with them a few times, but in this cases you can simply complete it once you catch up.

Harsha, we're sorry to hear that you no longer wish to use Todoist Premium because of that and if you want to receive a refund, please send us the order reference ID of your payment.

Best regards,

Harsha Bharadwaj
Replied on Mar 26, 2014 - 14:02 UTC


1. For the phone call case, I would not set it as a recurring task unless I want to make a call everyday. In that case, it makes sense to check-off one instance when done.

2. For the trash case, I would not be using 'every' in my repetition at the first place. Anyone who does not want to collect trash in 3 parts would use 'after' ;-)

So, its clearly a bug in the core logic. This happens in the case of 'recurring task' + 'every' occurrence.

And my order reference is 'ch_3hvcYZkkKfMOEg'

Hope to return back soon :-)

Todoist Lover,

David Trey  staff
Replied on Mar 26, 2014 - 14:41 UTC


Your payment has now been refunded.

Best regards,

Joey  premium
Replied on Mar 26, 2014 - 15:42 UTC

Again, I agree with Harsha. And, just because you say it's not a bug doesn't make it true. It's a logical mistake. A bug.

If we wanted to make the task re-occur from the COMPLETION date we would set the task up that way. These tasks are based on the DUE DATE. Again, DUEDATE of yesterday plus ONE DAY = TODAY. Period.

I, too, will want a refund. While your service is superior to RTM (and ToodleDo) in many ways, at least they get the core logic correct. Now I only hope they can update their UI and interface with GMail soon.

I will provide you my order reference soon.

Joey  premium
Replied on Mar 26, 2014 - 15:48 UTC

Also, based on your example: "This is not a bug. If you set a task to "make a phonecall" and won't reach this person for 3 days, when you do reach them on day 4, you will not call them 4 times and check off each instance of the "make a phonecall" task."

Don't you think it's a little presumptuous for you, a productivity tool developer, to try to dictate how I work?? Your attitude here is revealing. It is simply not within your purview to decide for me that I don't want to call them 4 times! How do you know what want?? And how dare you override my recurrence desires because you suspect that I probably didn't want that task in my task list 4 times? If I set up a recurring pattern that would place it in my task list 4 times, then that's what I want -- you have no right to override it.

Joey  premium
Replied on Mar 26, 2014 - 16:09 UTC

I will make one last point then I'll not write about this bug on these forums again: The simple solution/compromise to your desire to control the task and have your system not create 3 additional tasks in your example above is to simply embrace the notion that, upon completion of an everyday task that repeats based on DUE date is you insert the task on the soonest viable, non overdue, day -- which includes today.

So, in your example, the daily task, based on due date, "Make a phonecall", was due 4 days ago. It was marked complete today. Quick date math of the soonest viable option would have you system inserting the new task into the task database for TODAY.

"Today" isn't past due and is where the new daily task must be inserted to adhere at least somewhat to your customers' desired logic.

silvo  premium
Replied on Oct 10, 2014 - 11:44 UTC

I agree with Joey on the behaviour that 'every day' should have.
On the other hand I understand your logic too.

Is there any chance to get both behaviours, so that the user can decide what should happen to a specific task if he wants too?


Thomas Graungaard
Replied on Oct 19, 2014 - 00:04 UTC

I have similar issue, and would appreciate a suggestion for a smarter work-around than what I have come up with so far.

I have a task I need to complete every night at 11pm (verify backup completed successfully). Originally I had it as a daily task with no specific time, and if I was just 1 hr late checking it off, it disappeared for the following day. I then specified the time to every day at 11pm, in the hope that if I check it off at 1am, it would still recur at 11pm the same day. No such luck.

My workaround for now, is creating 7 tasks, one recurring every Monday, one recurring every Tuesday, etc.. but it's not the most elegant workaround.

Joey  premium
Replied on Oct 20, 2014 - 00:56 UTC

Thomas, that is exactly the same solution I came up with to offset this BUG in Todoist. It's still crazy to me that Todoist refuses to fix this bug. Remember The Milk handles it properly as well as a number of other task list managers.

If I want a task due EVERY 1 day I'm not asking for it to be repeated AFTER 1 day under any circumstance -- if I did, I'd set the task to repeat AFTER 1 day.

This is a bug and it bothers the heck out of me that not only will Todoist not fix it, they won't even acknowledge it, instead calling it a "philosophical" difference. It's a bug of bad and inconsistent logic.

pawelsubko  premium
Replied on May 28, 2015 - 14:47 UTC

I also totally don't get it. Everybody says them it's a bug and they keep claiming it's ok xD