> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/build/workflows/steps/time-of-day.md).

# Time of Day Step

Retired step that held workflow execution until a specific time of day was reached.

{% hint style="warning" %}
**The Time of Day step has been retired.** It can no longer be added to a workflow, and one left in an existing workflow no longer holds anyone — leads that reach it continue straight to the next step. The editor shows the step as an error, and the workflow can't be saved or published until the step is deleted. Use an [Send Email Step](https://docs.spara.com/build/workflows/steps/send-email.md) instead — it holds a send until the window reopens, in the lead's own timezone or one you choose.
{% endhint %}

The **Time of Day** step held a lead at a point in the workflow until a configured clock time was reached. [Send Email Step](https://docs.spara.com/build/workflows/steps/send-email.md) replace it: they apply the same restriction to the step that actually sends, in the lead's own timezone or one you choose, and hold the send until the window reopens instead of releasing the lead at a fixed hour.

If a workflow of yours still has one, open the step and delete it, then save and publish.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spara.com/build/workflows/steps/time-of-day.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
