We’ll begin this article by explaining the primary term - Task Run.
So, what are the Task Runs?
Task Runs are triggered tasks; tasks that you have scheduled, triggered by an event, or started manually.
The task run is counted once the task trigger is activated. Every time the tasks are activated/triggered by an event, schedule, or manually it will be considered a Task run.
Triggered Tasks = Task Runs
Task Runs are consumed when you start a task to send actual data from A to B. Tasks can be triggered on the event or scheduled.
E.G., If you schedule your Task to send Facebook leads to CRM every 2 hours, you’ll have 12 triggers a day (regardless of how many leads were sent or how many steps in the task you have).
And that’s the most important thing - what, and how many times.
So, the formula for the Task Runs would be:
F = ET x N
F = number of Task Runs
E.T. = number of tasks
N = number of triggers (how many times one task has been performed)
To make this as clear as possible, let us define our terms, The Task, and The Trigger.
What is the task?
The Task: The Task itself is the workflow that you create. Every flow will perform operations and send data from A to B to C…
You can also set your tasks to be triggered by some other occasion or manually.
What are the triggers?
The triggers are actions that will set your task to run. You can also set your tasks to be triggered by some other occasion or manually.
Your tasks can be triggered by:
a) Event
b) Schedule
c) Manual task run (when you manually run the task by clicking the run button)
Definition of Event: Some happening that took place in an external system that activated the task on the SyncSpider platform, and sent the data of the given action.
Definition of Schedule: Basically with our On Schedule trigger, you can set your task to activate at the exact specified time of the day, month, ... This will mean that at the given time the task will automatically recognize the set parameter and will trigger.
For example, you can set your task to activate every day every 15 minutes. You are free to determine which schedule option suits you the best.
Note - It is highly recommended that if you are using a High-Traffic Shop in the task, instead of selecting On Event trigger, you select On Schedule. It is directly preventing the task from getting broken and preventing our queue from getting jammed. Also, an important note is that in this way you are sparing the number of Task Runs you have in your plan.
What is important to mention is that Task Runs have nothing to do with Items within your Entity.
Your Entity may have 100 Items within it, and if you choose to send these data from point A to point B and run it every 6 hours, it will be counted as 4 Task Runs a day.
E.G.
If you schedule your Task to send Facebook leads to CRM every 2 hours, you’ll have 12 triggers a day (regardless of how many leads were sent or how many steps in the task you have).
We hope this article was helpful! For more information, you can always contact our support team.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article