> ## Documentation Index
> Fetch the complete documentation index at: https://developer.watson-orchestrate.ibm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrating to the new scheduling approach

Migrate from the old scheduling approach with intrinsic tools to the new Chat UI-based scheduling. The previous method required you to manually integrate intrinsic tools (`i__get_schedule_intrinsic_tool__`, `i__delete_schedule_intrinsic_tool__`, `i__get_flow_status_intrinsic_tool__`) into your agents. These tools are now deprecated and you no longer need them.

## Migration steps

<Steps>
  <Step title="Remove old intrinsic tools">
    Remove the deprecated tools from your code:

    * `i__get_schedule_intrinsic_tool__`
    * `i__delete_schedule_intrinsic_tool__`
    * `i__get_flow_status_intrinsic_tool__`
  </Step>

  <Step title="Configure agents or agentic workflows as schedulable">
    Enable scheduling by adding the appropriate flag to your agentic workflows and agents.

    **For agentic workflows:**

    Add `schedulable=True` to the `@flow` decorator:

    ```python theme={null}
    from ibm_watsonx_orchestrate.flow_builder.flows import flow

    @flow(
        name="my_flow",
        schedulable=True  # Add this flag
    )
    def my_workflow():
        # Workflow logic
        pass
    ```

    **For agents:**

    Add `is_schedulable=True` to the agent configuration:

    ```python theme={null}
    from ibm_watsonx_orchestrate.agent_builder.agents import Agent

    my_agent = Agent(
        name="my_agent",
        is_schedulable=True,  # Add this flag
        tools=["my_flow"],  # Include your schedulable workflow
        # other configuration...
    )
    ```
  </Step>

  <Step title="Redeploy">
    After you make these changes:

    1. Import your updated agent or agentic workflow. For more information, see:
       * [Importing tools](/tools/deploy_tool)
       * [Importing Agents](/agents/import_agent)

    2. Test scheduling to ensure it works correctly.

    3. Deploy to your live environment when ready.
  </Step>
</Steps>