You can add schedules to Managed Deep Agents. Add a schedule file to schedules/ with a cron expression + a prompt Deploy …And the agent runs itself Docs: https://docs.langchain.com/langsmith/python/managed-deep-agents-schedules… Demo from @ndrezn

Add schedules to Managed Deep Agents - Docs by LangChain

Source: https://docs.langchain.com/langsmith/python/managed-deep-agents-schedules Managed Deep Agents can run agents on a cron schedule. When you deploy the project,mda deployprovisions each schedule as a LangSmith cron after the deployment is live.

Project structure

Schedule declarations live in the project-levelschedules/directory, with one schedule per file:

Add a schedule

The file name becomes the managed schedule name.The schedule module must define a namedscheduledeclaration.

schedules/daily_digest.py

Configure schedule input

Each schedule must define exactly one of:

• prompt: A natural-language prompt. Managed Deep Agents converts it to a user message when the cron fires.
• input: A structured LangGraph input object. Use this when you need to pass custom graph input instead of a single prompt.

schedules/nightly_sweep.py

cronmust be a standard five-field cron expression: minute, hour, day of month, month, and day of week. Iftimezoneis omitted, LangSmith crons use UTC.

Choose thread behavior

Schedules use ephemeral threads by default. Managed Deep Agents creates a fresh thread for each run and asks LangSmith to delete that temporary thread after the run completes.Use a persistent thread only when scheduled runs should accumulate durable thread state across invocations.A persistent thread ID must be the UUID of a thread that already exists on the deployment. Managed Deep Agents passes the value straight to the Agent Server, which rejects any ID that is not a UUID.

Create the persistent thread

Create the thread before you deploy the schedule. Open the deployment inLangSmith Studio, create a new thread, and copy its thread ID.mda deployprints the deployment URL, and LangSmith lists it on the deployment page.Neither Managed Deep Agents nor themdaCLI creates the thread, so this is a one-time manual step for each persistent schedule.

Declare the persistent schedule

Use that thread ID in the schedule declaration.

schedules/nightly_memory.py

Deliver results to Slack

Setdeliver\_toto post the final response through a configuredSlack channel.Use a Slack channel ID because scheduled runs have no originating thread.

schedules/monday_greeting.py

The Slack bot must have access to the destination.

Use static declarations

Schedule declarations are extracted at compile time. Keep schedule configuration statically serializable:

• Use literals, lists, dictionaries, and references to top-level literal constants.
• Do not read environment variables, call functions, use\*\*kwargs, or compute schedule values dynamically.
• Put dynamic behavior in the agent, tools, middleware, or runtime context instead.

Test schedules locally

mda devcompilesschedules/and lists each schedule in its startup banner, but it does not provision them. Schedules run only on a deployment.

To test the agent behavior a schedule triggers, send the schedule’spromptorinputto the agent directly in local Studio. To test the schedule itself, deploy the project to a development deployment.

Deploy schedules

Test the project locally withmda dev, then deploy it withmda deploy. Open deployment traces in LangSmith to inspect model calls, tool calls, errors, and latency.When the deployment reachesDEPLOYED,mda deploysearches for existing Managed Deep Agents-owned cron jobs on the deployed Agent Server, deletes them, and creates cron jobs for the currentschedules/declarations. Removing a local schedule file and redeploying removes the corresponding managed cron.

Troubleshoot schedules

• must export a named schedule declaration: Define a top-levelschedulein each file inschedules/.
• must define exactly one of prompt or input: Add eitherpromptorinput, but not both.
• cron must be a standard 5\-field expression: Use five cron fields, not seconds-based cron syntax.
• schedule is not static: Replace computed values with literals or top-level literal constants.
• failed to create cron for schedule: Open the deployment URL in LangSmith and confirm the deployed Agent Server is healthy.
• Invalid thread ID: must be a UUID \(HTTP 422\): A persistent schedule declares a thread ID that is not a UUID. Replace it with the UUID of an existing thread. SeeChoose thread behavior.
• A schedule does not run during local development:mda devdoes not provision schedules. SeeTest schedules locally.

Next steps