How do I stop getting "Task was stopped because its Zap was turned off during its execution." errors?

Hi - thanks for the reply. I understand how to disable email notification but this does not solve my problem because then I will also lose all notifications for my other Zaps which are working fine.

The problem I have is why I am getting any alerts at all on a Zap which is disabled. Surely they are disabled and should not be running? I assume they are using resources so who is paying for this - Zapier or me? How I stop these delayed tasks from running? It seems the only way to stop them is to delete the Zap entirely. 

This never used to work like this, something has changed in the last month. Any ideas?

Hey @Troy Tessalone - here’s the Zap:
 

Here’s the error:

I’m sure the problem relates to the Append Entry stage which is awaiting up to 10 Tweets. I can see tasks queued in the Task Waiting state which I guess should be stopped instead of left waiting. If I delete all those tasks the alerts eventually stop coming some days later :) 

Cheers,
Colin 

@colindomoney 

The Zap Run errors are likely related to the Delay behavior and the Zap being turned OFF, which then causes the Zap Runs “delay” to hit an error because it can’t finish processing.

Digest and Zap History

In your Zap History, you’ll see individual Zap runs for each time the Zap was triggered, not only for when the digest is released.
The first Zap run in the Zap will have a status of Delayed until the digest releases (according to the frequency settings).
When the digest is released, the status of the Zap run will change to Success.