---
title: "Schedule your first task"
canonical: https://workspace.socra.com/docs/tasks/get-started
---

# Schedule your first task

Give your agent one recurring check with a clear result. The agent creates and manages the task using its own identity.

## Before you start

You need a [Socra Agent ready to work](/docs/agents/get-started), with access to the material it should check and the conversation where it should report. Scheduled work uses the agent's model connection and is subject to its availability and usage limits.

## Describe the work

Send an instruction in your conversation with the agent. For example:

> Every weekday at 9 AM America/Chicago, review the open Cortex Issues assigned to you. Tell me in this conversation only when something is blocked or needs my decision. Create the recurring task under your own identity and confirm its next run time.

Name the time zone and what counts as a useful update. The agent needs permission to read the Issues and send a message in that conversation.

## Create the task

The agent can use the managed Socra CLI in its environment. An equivalent command is:

```sh
socra task create "Review assigned issues" \
  --cron "0 9 * * 1-5" \
  --timezone America/Chicago \
  --description "Review my open Cortex Issues. Report in the source conversation only when work is blocked or needs a decision. Complete this occurrence after the review." \
  --context "CONVERSATION_URL"
```

Replace `CONVERSATION_URL` with the authorized source conversation's URL. It provides a reference for the agent; it does not grant access or automatically send a message.

The command must run as the agent that will do the work. A task created with your personal CLI session belongs to you.

## Verify the schedule

Ask the agent for the returned task ID and `next_run_at`. Have it retrieve the task, replacing `TASK_ID` with that ID:

```sh
socra task get TASK_ID
```

Confirm that the task is `pending`, `schedule_paused` is `false`, and the schedule contains the intended cron expression and time zone. `next_run_at` is a timestamp; compare it in the chosen time zone.

## Complete a run

After a due time, the agent can inspect the occurrence history:

```sh
socra task occurrence list TASK_ID
```

After it has actually done the work, it completes that occurrence. Replace `OCCURRENCE_ID` with the ID from the history:

```sh
socra task occurrence complete OCCURRENCE_ID
```

The occurrence should now be `completed`, while the recurring task remains active. A delivered event alone does not mean the work is finished. Leave failed or blocked work incomplete.

## Pause or stop

Ask the agent to pause the reminder when it is no longer needed temporarily:

```sh
socra task pause TASK_ID
```

Use `socra task resume TASK_ID` to resume scheduling, or `socra task complete TASK_ID` to end the entire series. Verify the resulting state with `socra task get TASK_ID`.

If a run does not happen, see [Check a missed run](/docs/tasks/scheduling#check-a-missed-run). For a different cadence, read [Schedules and occurrences](/docs/tasks/scheduling).