How to optimize your Task Run consumption?

Erstellt von Nikola Milosavljevic, Geändert am Wed, 13 Jul 2022 um 09:54 AM von Nikola Milosavljevic

The number of Task Runs will depend on the number of times the task has taken some action. 

 

The Task Run happens when a task runs on a schedule, when it is manually triggered, or triggered by an event (trigger). 

 

The best way to keep it under control is to decrease the number of triggers. And here is how you can do that:

 

Reduce triggers by increasing the interval. 

 

You can reduce the number of Task Runs by reducing the frequency of task runs. That’s the simplest and most effective way. For example, maybe you don’t need your task to run every 2 hours. You can schedule it to run every 6 hours. Or perhaps it will be enough to run only once or twice a day. 

 

E.G.

 

If you have a task running every 2 hours, within 1 day, you will have 12 Task Runs, and within a month, you will have 360 or 372 Task Runs. 

 

But if you run the same task once a day, you will have 1 Task Run a day and only 30 or 31 Task Runs a month.

 

Set the task runs only when needed change happens

 

E.G.

 

If you are just at the beginning of your eCommerce journey, with a small scope of work, and you set the task to send orders from your Shopify webshop to your local database, you can schedule the task runs only when the purchase happens. 

 

We hope that this article will help you optimize your Task Run consumption, and if you need any additional information, our support team is always available to answer your questions. 

War dieser Artikel hilfreich?

Das ist großartig!

Vielen Dank für Ihr Feedback

Leider konnten wir nicht helfen

Vielen Dank für Ihr Feedback

Teilen Sie uns mit, wie wir diesen Artikel verbessern können!

Wählen Sie wenigstens einen der Gründe aus

Feedback gesendet

Wir wissen Ihre Mühe zu schätzen un werden versuchen, den Artikel zu korrigieren