> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/itential-platform/6/studio/tasks/reference/stub/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# stub

> Use the stub task as a placeholder in a workflow to represent tasks that have not yet been implemented.

The `stub` task is used as a placeholder or "stand-in" type of task in a workflow.

## Potential use case

Suppose you are building a workflow and you identify some gaps in your high-level design, but you don't want to stop to work out the details where those gaps exist. You could use the `stub` task as a placeholder, and once you've stubbed the placements that you need, go back and replace those stand-in tasks with a real task or a set of tasks that perform what your workflow is designed to do.

## Properties

| Incoming   | Type   | Description                                                                           |
| ---------- | ------ | ------------------------------------------------------------------------------------- |
| `type`     | Enum   | Required. The type of transition to emulate. Allowed values are `error` or `success`. |
| `delay`    | Number | Represents the number of seconds to wait or delay the response.                       |
| `response` | String | The response to pass through the stub.                                                |

| Outgoing   | Type   | Description                    |
| ---------- | ------ | ------------------------------ |
| `response` | String | Response output from the stub. |

## Example

In this example, the `type` reference variable is set to `"success"`. The job can also be set to `"error"`, in which case an error is returned as the response instead of a clean and complete automation. The `delay` is set to `12`, which shows in the automation as a delay of 12 seconds. The response to pass through is the word "awesome".

![](/_fern-img/aac0fdc3857f97923e749494539ddc9fa151bb9ebba22908e320a60450d8c2ec.webp)

The `response` that returns for this `stub` is the word "awesome", which completed after a 12-second delay. You can view the 12-second delay in **Job Manager** as the job is running.

![](/_fern-img/0b46f28d270d890b372eff1e25221831a7d6d4a887a456ce8c656298c5287594.webp)

> Use the stub task as a placeholder in a workflow to represent tasks that have not yet been implemented.