What are Tasks? #
Cyclr records a “Task” when it makes an API call to an external system, or executes certain types of Steps within your integrations (your Templates and Cycles).
If your Cyclr Console is hosted on a Shared Cyclr Instance, you’ll have a Monthly Task Allowance which is included in your Cyclr subscription. Executing more Tasks than your Monthly Task Allowance will result in additional charges.
Your Console’s Dashboard shows the number of Tasks used in the current billing period.
You can create Notifications within your Cyclr Console so that you and your colleagues receive emails to keep track of your usage.
Tasks are classified as follows, and both count towards your Monthly Task Allowance, if applicable:
- Successful Tasks – when an action executes correctly, for example an HTTP 2xx Status Code is received from an API call.
- Incident Tasks – if an error is encountered, typically by an HTTP 4xx or 5xx Status Code being received or other error.
When are Tasks recorded? #
Not all actions cause Cyclr to record a Task – the table below gives more details:
| Action / Event | Successful Tasks recorded? | Incident Tasks recorded? |
|---|---|---|
| Executing a Step using a Connector Method of type Action – makes an HTTP request | Yes | Yes |
| Executing a Step using a Connector Method of type Webhook – receives an HTTP request | Yes | Yes |
| Executing a Step using a Connector Method of type Webhook Response – sends back an HTTP response | Yes | Yes |
| Executing a Step using a Method of type Script – executes JavaScript code | No (Script steps themselves do not count) | No |
Executing the http_request() Script function (whether inside a Script Method or Step-level Script) | Yes | Yes |
| Executing a Step that uses a Tool (Decision, Delay, Wait, etc.) | No | Yes |
| Executing a Connector Method via Data on Demand | Yes | Yes |
| Calling a Cyclr MCP Server‘s Tool | Yes | Yes |
| An LLM calling multiple MCP Server Tools (each call counted individually) | Yes (per tool call) | Yes |
Note: When working with MCP Servers, an external Large Language Model (an “LLM”) may call multiple MCP Server “Tools” in what appears to be a single process from within the LLM, but will result in multiple Tasks being recorded within Cyclr.
Summary #
- Most Connector-based actions – log Successful Tasks unless they encounter an error.
- Tools (Decision/Delay/Wait) – only log Incident Tasks when they fail.
- Script steps – don’t count, but
http_request()calls inside them do. - MCP Server Tools – each invocation counts, even if triggered by an LLM in one “logical” operation.