> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow schedules and public forms

> Run a deployed Hive workflow on an hourly, daily or weekly schedule, or collect submissions from anyone with a public form link.

Schedules and public forms start **production runs** of a workflow's live release. Both need the
workflow deployed and live: a draft or paused workflow starts no runs from them. See
[Test and deploy](/workflows/test-and-deploy).

## Schedules

Open the **Scheduled** tab to see every saved schedule you can manage.

### Create a schedule

<Steps>
  <Step title="Start a schedule">
    Select **New schedule** and choose the workflow. Give the schedule a label (up to 120
    characters).
  </Step>

  <Step title="Choose when">
    * **Hourly** — at the minute you choose, every hour;
    * **Daily** — at the hour and minute you choose;
    * **Weekly** — on the days you choose, at the hour and minute you choose.
  </Step>

  <Step title="Set the timezone">
    Enter an IANA timezone such as `Europe/London` or `America/New_York`. The schedule follows local
    time, including daylight-saving changes.
  </Step>

  <Step title="Create it">
    Leave **Start enabled** on to arm it now, then select **Create schedule**.
  </Step>
</Steps>

Each row shows the workflow, the cadence (for example "Mon, Wed · 09:00"), the next run, when it
last ran and its timezone. Next and last run times are shown in UTC; how a run went is in the
workflow's run history.

### Manage a schedule

* The row's switch turns the schedule on or off without deleting it.
* **Edit** changes when it runs. **Delete** stops its future runs; past runs keep their receipts.
* **Run now** starts a production run immediately, as you, using your own connected accounts. It is
  refused, with the reason, when the workflow is not deployed or is paused.

### Whose accounts a schedule uses

A scheduled run acts as the member who created the schedule, through their connected accounts, and
only while they still have the **Operator** role or higher. The schedule is pinned to the release
that member scheduled and follows their own later deploys. If someone else's release becomes live,
the schedule stops and waits for its owner to review and turn it back on — nobody's accounts run a
version they have not seen. An admin can turn another member's schedule off, but never on.

### Schedule triggers

A workflow whose trigger is **Schedule** runs on the trigger's own cadence, in UTC, once deployed —
but only while it has no saved schedules. Saved schedules work with any trigger and take over from
the trigger's cadence.

## Public forms

A public form lets anyone with its link submit the form without a Hive account. Each submission
starts one production run.

### Publish a form link

<Steps>
  <Step title="Use a Public form trigger">
    Select the trigger, choose **Public form**, add the title and fields, and optionally a
    confirmation message. See [Triggers](/workflows/workflow-steps#triggers).
  </Step>

  <Step title="Deploy">
    [Deploy](/workflows/test-and-deploy#deploy-a-release) the workflow.
  </Step>

  <Step title="Create the link">
    Select **Form link** in the builder header, then **Create form link**.
  </Step>

  <Step title="Copy and share">
    The link is shown only while the dialog is open. If you need it again later, create a new one.
  </Step>
</Steps>

The link opens a Hive-hosted page at `/forms?token=…` on your Hive app address. To submit from your
own site or another system instead, use the [public form API](/developers/public-form-api).

### When a link stops working

A link belongs to the release that was live when it was created. It stops working when:

* a new link is created;
* the workflow is deployed again, or another version is re-activated;
* the workflow is paused, returned to draft or deleted;
* the workflow's owner can no longer run it.

A visitor then sees **This form is not available** and is asked for a new link. Changes to the form
reach visitors only after you deploy — which ends the current link, so create and share a new one.

### Runs from a form

A submission runs as the workflow owner, through the owner's connected accounts, and its actions go
through your approval and safety policy like any other production run. A workflow started by a
public form cannot run a **Saved agent** step.

Submissions are kept with the workflow, so a member with the **Operator** role or higher can replay
one of the last 20 in a test run from the trigger's **Test** tab.

<Warning>
  Anything a visitor types reaches your workflow as untrusted input. It can steer an AI condition or
  an agent's answer, so keep approvals on actions that matter.
</Warning>

## Related

<CardGroup cols={2}>
  <Card title="Public form API" icon="code" href="/developers/public-form-api">
    Submit forms from your own site or system.
  </Card>

  <Card title="Scheduled tasks" icon="clock" href="/library/scheduled-tasks">
    Every scheduled agent and workflow in one place.
  </Card>

  <Card title="Test and deploy" icon="rocket" href="/workflows/test-and-deploy">
    Releases, pausing and notifications.
  </Card>

  <Card title="Triggers and steps" icon="list" href="/workflows/workflow-steps">
    Form fields and schedule settings.
  </Card>
</CardGroup>