Is it possible to cancel or drop a single Task?

This is exactly the workaround I currently use for this.

The “@dropped” context itself is set as “on hold” status. I wish I could use the “dropped” status, but this results in OF1 doesn’t show it in the list of contexts I can set an action to. If OF2 does the same (which I didn’t check yet), then it doesn’t seem to be a problem with DB format–but only with how existing status is interpreted (attn @lizard).

I do not use any special contexts for cancelled tasks.
Do not like the idea to change an original context with something artificial…

Currently, if I decide to cancel the task then I do this steps:

  • mark the task as “Done”;
  • date of completion is set to “Today” - since I cancelled this task TODAY;
  • add a postfix like “[cancelled - %reason%]” (or simply “[leave it]”).

“Repair the laptop” -> “Repair the laptop [cancelled - bought a new one]”
“Run 10 km” -> “Run 10 km [leave it]”

Basically I use OF in iPad.
And in iOS a task’s note is not visible in the tasks list - you have to open the task to see it.
That’s why I AM TRYING NOT USING NOTES - everything is specified in “[…]” and is displayed in tasks list.

Of course, I cannot see all these cancelled tasks in a perspective…
Actually, usually I do not need to reconsider these cancelled tasks.
But there is a workaround: if you always use postfix “[cancelled …]” then you can list all these cancelled tasks by simple search.

1 Like


+1 for this feature. I have a task in a sequential flow, and i need to cancel the task. But, i don’t want to lose the history of this task, or remove it from it’s current position. Just gray it out, and treat it as if it’s not there (in terms of project completion).

One reason is that i might want to activate it later.


We’ve long planned to add both “On Hold” and “Dropped” states for individual tasks just like we have on projects, we just need to implement backwards- and forwards-compatible syncing first to let people transition from the less featureful data format to the newer data format.

Transitioning to this new sync format is our next major milestone (on both Mac and iOS), and will make it possible for us to move forward with planned changes like this one. I’m looking forward to it!


The set of new statuses to be added: is it finalized now, or still open for input from users?

Well, these states aren’t really new: both already exist on projects, so their behavior is well-defined, have translations in all our languages, have icons and documentation that explain what they mean, etc.

That said, if you have more states you’d like to suggest please do let us know!

Hi kcase, do you have an expected date for this? OF moved to a new sync encrypted format last year so it should be possible now to have dropped tasks.

I guess is it expected behaviour that it is not possible to set dropped state context to a task. I understand that as the context is dropped it does not appear in the list, but at least OF should allow to set it (by writing the dropped context name)

The file format is no longer blocking us, so this year we’ve been making fundamental improvements to our file format, starting with faster attachment syncing (now shipped), support for multiple tags, and more flexible repeats and notifications. Dropping tasks is a pet wish of mine, but it hasn’t been requested so frequently yet as to make this year’s official roadmap. (But we might manage to fit it into this year’s database changes anyway.)


💜 great response!

1 Like

Any new Improvements on this issue?

Summing up this discussion: 1- Thread

1 Like

I’m not certain if this is the right place, even after reading through most of the replies to this old post, but here it goes: I also would like to know in the current Omnifocus if this is possible, that is to cancel or mark as not done a task that is part fo a repeatable task.

For example, perhaps I’m using some of my tasks as personal improvement goals (I figure I should probably make that a context, but I’m super new to Omnifocus and trying to decide if I’ll keep working with it versus Firetask, and so far I think I will.) So for now I may have a repeatable task to run every Saturday and walk every two days. What I want is to be able to say that I missed doing a task, but then have the next repeat of that task show up.

I’ve been reading old blogs and this one, but still can’t figure out how to do this. Thanks for any suggestions.

Tada, perhaps this is the answer to my question and I hope to anyone else wondering:

That said, if anyone has solutions in addition to this post, I’m a taker (as well as a giver). ;)

I would see this as a fundamental and necessary feature to drop an action since I want to see in review which of my actions in a project I had completed and which I had considered but dropped. Any insights when this will be available? How/Where can I vote for this feature?

With the introduction of multiple tags, I have created a ‘Dropped’ tag. I apply this tag and then mark the action(s) as complete. The multi-rule perspectives enable retrieving all these dropped tasks.

This makes use of a convention, rather than a built-in property, but I think this is absolutely fine. An alternative is to move an action or a branch of actions to a project which has the ‘dropped’ status.

1 Like

For now your best option is to use a convention to identify your dropped tasks (like the “Dropped” tag @MultiDim suggests above), but we think Dropped will be an important state to communicate when sharing linked tasks. Linked tasks were originally part of last year’s roadmap, but we ran out of time—so they’re now planned for this year.