remove auto-start

Author: khadni

reports/llms-report.json

@@ -1,22 +1,22 @@
 {
-  "startedAt": "2025-11-11T16:44:03.554Z",
+  "startedAt": "2025-11-11T18:19:12.241Z",
   "siteBase": "https://docs.chain.link",
   "sections": [
     {
       "section": "cre-go",
       "pagesProcessed": 84,
       "outputPath": "src/content/cre/llms-full-go.txt",
-      "bytes": 633140,
-      "prevBytes": 633220,
-      "deltaBytes": -80
+      "bytes": 631094,
+      "prevBytes": 633140,
+      "deltaBytes": -2046
     },
     {
       "section": "cre-ts",
       "pagesProcessed": 79,
       "outputPath": "src/content/cre/llms-full-ts.txt",
-      "bytes": 588554,
-      "prevBytes": 588686,
-      "deltaBytes": -132
+      "bytes": 586508,
+      "prevBytes": 588554,
+      "deltaBytes": -2046
     },
     {
       "section": "vrf",
@@ -123,5 +123,5 @@
       "deltaBytes": 0
     }
   ],
-  "finishedAt": "2025-11-11T16:44:07.573Z"
+  "finishedAt": "2025-11-11T18:19:16.291Z"
 }

src/content/cre/guides/operations/activating-pausing-workflows.mdx

@@ -33,15 +33,7 @@ The `cre workflow activate` command changes a paused workflow's status to active
 
 ### When to activate
 
-You typically use `activate` in these scenarios:
-
-- **After pausing a workflow**: To resume execution after maintenance or debugging
-- **Manual deployment**: When you deployed with `--auto-start=false`
-
-{/* prettier-ignore */}
-<Aside type="note" title="Auto-start by default">
-  Most workflows are automatically activated during deployment because `cre workflow deploy` uses `--auto-start=true` by default. You only need to manually activate workflows that were deployed with `--auto-start=false` or that have been paused.
-</Aside>
+You typically use `activate` after pausing a workflow to resume execution after maintenance or debugging.
 
 ### Usage
 

src/content/cre/guides/operations/deploying-workflows.mdx

@@ -68,7 +68,6 @@ cre workflow deploy my-workflow --target production-settings
 | Flag             | Description                                                                             |
 | ---------------- | --------------------------------------------------------------------------------------- |
 | `--target`       | Sets the target environment from your configuration files (e.g., `production-settings`) |
-| `--auto-start`   | Activate the workflow immediately after deployment (default: `true`)                    |
 | `--output`       | The output file for the compiled WASM binary (default: `"./binary.wasm.br.b64"`)        |
 | `--unsigned`     | Return the raw transaction instead of broadcasting it to the network                    |
 | `--yes`          | Skip confirmation prompts and proceed with the operation                                |
@@ -138,12 +137,6 @@ Details:
    Config URL:          https://storage.cre.example.com/artifacts/<workflow-id>/config
 ```
 
-<Aside type="note" title="What is auto-start?">
-  By default, the `cre workflow deploy` command uses the `--auto-start=true` flag. This means that as soon as your
-  workflow is successfully registered onchain, it will also be immediately activated and ready to be triggered. You can
-  disable this behavior by passing `--auto-start=false`.
-</Aside>
-
 ## Verifying your deployment
 
 After a successful deployment, you can verify that your workflow was registered correctly in two ways:

src/content/cre/guides/operations/updating-deployed-workflows.mdx

@@ -42,14 +42,6 @@ cre workflow deploy my-workflow --target production-settings
   CRE does not currently maintain workflow version history. When you redeploy a workflow with the same name, it completely replaces the previous deployment. You cannot roll back to a previous version through the CLI.
 </Aside>
 
-### Auto-start behavior
-
-By default, `cre workflow deploy` uses `--auto-start=true`, which means the updated workflow is automatically activated after deployment. If your workflow was previously paused and you want it to remain paused after the update, use `--auto-start=false`:
-
-```bash
-cre workflow deploy my-workflow --auto-start=false --target production-settings
-```
-
 ## Best practices for updates
 
 1. **Test locally first**: Always test your changes using `cre workflow simulate` before deploying to production

src/content/cre/llms-full-go.txt

@@ -4865,7 +4865,6 @@ cre workflow deploy my-workflow --target production-settings
 | Flag             | Description                                                                             |
 | ---------------- | --------------------------------------------------------------------------------------- |
 | `--target`       | Sets the target environment from your configuration files (e.g., `production-settings`) |
-| `--auto-start`   | Activate the workflow immediately after deployment (default: `true`)                    |
 | `--output`       | The output file for the compiled WASM binary (default: `"./binary.wasm.br.b64"`)        |
 | `--unsigned`     | Return the raw transaction instead of broadcasting it to the network                    |
 | `--yes`          | Skip confirmation prompts and proceed with the operation                                |
@@ -4935,12 +4934,6 @@ Details:
    Config URL:          https://storage.cre.example.com/artifacts/<workflow-id>/config
 ```
 
-<Aside type="note" title="What is auto-start?">
-  By default, the `cre workflow deploy` command uses the `--auto-start=true` flag. This means that as soon as your
-  workflow is successfully registered onchain, it will also be immediately activated and ready to be triggered. You can
-  disable this behavior by passing `--auto-start=false`.
-</Aside>
-
 ## Verifying your deployment
 
 After a successful deployment, you can verify that your workflow was registered correctly in two ways:
@@ -4990,15 +4983,7 @@ The `cre workflow activate` command changes a paused workflow's status to active
 
 ### When to activate
 
-You typically use `activate` in these scenarios:
-
-- **After pausing a workflow**: To resume execution after maintenance or debugging
-- **Manual deployment**: When you deployed with `--auto-start=false`
-
-
-<Aside type="note" title="Auto-start by default">
-  Most workflows are automatically activated during deployment because `cre workflow deploy` uses `--auto-start=true` by default. You only need to manually activate workflows that were deployed with `--auto-start=false` or that have been paused.
-</Aside>
+You typically use `activate` after pausing a workflow to resume execution after maintenance or debugging.
 
 ### Usage
 
@@ -5172,14 +5157,6 @@ cre workflow deploy my-workflow --target production-settings
   CRE does not currently maintain workflow version history. When you redeploy a workflow with the same name, it completely replaces the previous deployment. You cannot roll back to a previous version through the CLI.
 </Aside>
 
-### Auto-start behavior
-
-By default, `cre workflow deploy` uses `--auto-start=true`, which means the updated workflow is automatically activated after deployment. If your workflow was previously paused and you want it to remain paused after the update, use `--auto-start=false`:
-
-```bash
-cre workflow deploy my-workflow --auto-start=false --target production-settings
-```
-
 ## Best practices for updates
 
 1. **Test locally first**: Always test your changes using `cre workflow simulate` before deploying to production
@@ -7476,38 +7453,26 @@ cre workflow deploy <workflow-name-or-path> [flags]
 
 **Flags:**
 
-| Flag               | Description                                                                                    |
-| ------------------ | ---------------------------------------------------------------------------------------------- |
-| `-r, --auto-start` | Activate the workflow immediately after deployment (default: `true`)                           |
-| `-o, --output`     | Output file for the compiled WASM binary encoded in base64 (default: `"./binary.wasm.br.b64"`) |
-| `--unsigned`       | Return the raw transaction instead of sending it to the network                                |
-| `--yes`            | Skip the confirmation prompt and proceed with the operation                                    |
+| Flag           | Description                                                                                    |
+| -------------- | ---------------------------------------------------------------------------------------------- |
+| `-o, --output` | Output file for the compiled WASM binary encoded in base64 (default: `"./binary.wasm.br.b64"`) |
+| `--unsigned`   | Return the raw transaction instead of sending it to the network                                |
+| `--yes`        | Skip the confirmation prompt and proceed with the operation                                    |
 
 **Examples:**
 
-- Deploy workflow with auto-start (default behavior)
+- Deploy workflow
 
   ```bash
   cre workflow deploy my-workflow --target production-settings
   ```
 
-- Deploy without auto-starting
-
-  ```bash
-  cre workflow deploy my-workflow --auto-start=false --target production-settings
-  ```
-
 - Deploy and save the compiled binary to a custom location
 
   ```bash
   cre workflow deploy my-workflow --output ./dist/workflow.wasm.br.b64
   ```
 
-
-<Aside type="note" title="Auto-start behavior">
-  By default, workflows are automatically activated after deployment (`--auto-start=true`). This means they're ready to respond to triggers immediately. Use `--auto-start=false` if you need to deploy without activating.
-</Aside>
-
 For more details, see [Deploying Workflows](/cre/guides/operations/deploying-workflows).
 
 ## `cre workflow activate`
@@ -7543,11 +7508,6 @@ cre workflow activate <workflow-name-or-path> [flags]
 cre workflow activate ./my-workflow --target production-settings
 ```
 
-
-<Aside type="note" title="When to use activate">
-  You typically use `activate` after deploying with `--auto-start=false` or after pausing a workflow. Most workflows are automatically activated during deployment.
-</Aside>
-
 For more details, see [Activating & Pausing Workflows](/cre/guides/operations/activating-pausing-workflows).
 
 ## `cre workflow pause`

src/content/cre/llms-full-ts.txt

@@ -3782,7 +3782,6 @@ cre workflow deploy my-workflow --target production-settings
 | Flag             | Description                                                                             |
 | ---------------- | --------------------------------------------------------------------------------------- |
 | `--target`       | Sets the target environment from your configuration files (e.g., `production-settings`) |
-| `--auto-start`   | Activate the workflow immediately after deployment (default: `true`)                    |
 | `--output`       | The output file for the compiled WASM binary (default: `"./binary.wasm.br.b64"`)        |
 | `--unsigned`     | Return the raw transaction instead of broadcasting it to the network                    |
 | `--yes`          | Skip confirmation prompts and proceed with the operation                                |
@@ -3852,12 +3851,6 @@ Details:
    Config URL:          https://storage.cre.example.com/artifacts/<workflow-id>/config
 ```
 
-<Aside type="note" title="What is auto-start?">
-  By default, the `cre workflow deploy` command uses the `--auto-start=true` flag. This means that as soon as your
-  workflow is successfully registered onchain, it will also be immediately activated and ready to be triggered. You can
-  disable this behavior by passing `--auto-start=false`.
-</Aside>
-
 ## Verifying your deployment
 
 After a successful deployment, you can verify that your workflow was registered correctly in two ways:
@@ -3907,15 +3900,7 @@ The `cre workflow activate` command changes a paused workflow's status to active
 
 ### When to activate
 
-You typically use `activate` in these scenarios:
-
-- **After pausing a workflow**: To resume execution after maintenance or debugging
-- **Manual deployment**: When you deployed with `--auto-start=false`
-
-
-<Aside type="note" title="Auto-start by default">
-  Most workflows are automatically activated during deployment because `cre workflow deploy` uses `--auto-start=true` by default. You only need to manually activate workflows that were deployed with `--auto-start=false` or that have been paused.
-</Aside>
+You typically use `activate` after pausing a workflow to resume execution after maintenance or debugging.
 
 ### Usage
 
@@ -4089,14 +4074,6 @@ cre workflow deploy my-workflow --target production-settings
   CRE does not currently maintain workflow version history. When you redeploy a workflow with the same name, it completely replaces the previous deployment. You cannot roll back to a previous version through the CLI.
 </Aside>
 
-### Auto-start behavior
-
-By default, `cre workflow deploy` uses `--auto-start=true`, which means the updated workflow is automatically activated after deployment. If your workflow was previously paused and you want it to remain paused after the update, use `--auto-start=false`:
-
-```bash
-cre workflow deploy my-workflow --auto-start=false --target production-settings
-```
-
 ## Best practices for updates
 
 1. **Test locally first**: Always test your changes using `cre workflow simulate` before deploying to production
@@ -6118,38 +6095,26 @@ cre workflow deploy <workflow-name-or-path> [flags]
 
 **Flags:**
 
-| Flag               | Description                                                                                    |
-| ------------------ | ---------------------------------------------------------------------------------------------- |
-| `-r, --auto-start` | Activate the workflow immediately after deployment (default: `true`)                           |
-| `-o, --output`     | Output file for the compiled WASM binary encoded in base64 (default: `"./binary.wasm.br.b64"`) |
-| `--unsigned`       | Return the raw transaction instead of sending it to the network                                |
-| `--yes`            | Skip the confirmation prompt and proceed with the operation                                    |
+| Flag           | Description                                                                                    |
+| -------------- | ---------------------------------------------------------------------------------------------- |
+| `-o, --output` | Output file for the compiled WASM binary encoded in base64 (default: `"./binary.wasm.br.b64"`) |
+| `--unsigned`   | Return the raw transaction instead of sending it to the network                                |
+| `--yes`        | Skip the confirmation prompt and proceed with the operation                                    |
 
 **Examples:**
 
-- Deploy workflow with auto-start (default behavior)
+- Deploy workflow
 
   ```bash
   cre workflow deploy my-workflow --target production-settings
   ```
 
-- Deploy without auto-starting
-
-  ```bash
-  cre workflow deploy my-workflow --auto-start=false --target production-settings
-  ```
-
 - Deploy and save the compiled binary to a custom location
 
   ```bash
   cre workflow deploy my-workflow --output ./dist/workflow.wasm.br.b64
   ```
 
-
-<Aside type="note" title="Auto-start behavior">
-  By default, workflows are automatically activated after deployment (`--auto-start=true`). This means they're ready to respond to triggers immediately. Use `--auto-start=false` if you need to deploy without activating.
-</Aside>
-
 For more details, see [Deploying Workflows](/cre/guides/operations/deploying-workflows).
 
 ## `cre workflow activate`
@@ -6185,11 +6150,6 @@ cre workflow activate <workflow-name-or-path> [flags]
 cre workflow activate ./my-workflow --target production-settings
 ```
 
-
-<Aside type="note" title="When to use activate">
-  You typically use `activate` after deploying with `--auto-start=false` or after pausing a workflow. Most workflows are automatically activated during deployment.
-</Aside>
-
 For more details, see [Activating & Pausing Workflows](/cre/guides/operations/activating-pausing-workflows).
 
 ## `cre workflow pause`

src/content/cre/reference/cli/workflow.mdx

@@ -94,36 +94,24 @@ cre workflow deploy <workflow-name-or-path> [flags]
 
 | <div style={{ width: "150px" }}>Flag</div> | Description                                                                                    |
 | ------------------------------------------ | ---------------------------------------------------------------------------------------------- |
-| `-r, --auto-start`                         | Activate the workflow immediately after deployment (default: `true`)                           |
 | `-o, --output`                             | Output file for the compiled WASM binary encoded in base64 (default: `"./binary.wasm.br.b64"`) |
 | `--unsigned`                               | Return the raw transaction instead of sending it to the network                                |
 | `--yes`                                    | Skip the confirmation prompt and proceed with the operation                                    |
 
 **Examples:**
 
-- Deploy workflow with auto-start (default behavior)
+- Deploy workflow
 
   ```bash
   cre workflow deploy my-workflow --target production-settings
   ```
 
-- Deploy without auto-starting
-
-  ```bash
-  cre workflow deploy my-workflow --auto-start=false --target production-settings
-  ```
-
 - Deploy and save the compiled binary to a custom location
 
   ```bash
   cre workflow deploy my-workflow --output ./dist/workflow.wasm.br.b64
   ```
 
-{/* prettier-ignore */}
-<Aside type="note" title="Auto-start behavior">
-  By default, workflows are automatically activated after deployment (`--auto-start=true`). This means they're ready to respond to triggers immediately. Use `--auto-start=false` if you need to deploy without activating.
-</Aside>
-
 For more details, see [Deploying Workflows](/cre/guides/operations/deploying-workflows).
 
 ## `cre workflow activate`
@@ -159,11 +147,6 @@ cre workflow activate <workflow-name-or-path> [flags]
 cre workflow activate ./my-workflow --target production-settings
 ```
 
-{/* prettier-ignore */}
-<Aside type="note" title="When to use activate">
-  You typically use `activate` after deploying with `--auto-start=false` or after pausing a workflow. Most workflows are automatically activated during deployment.
-</Aside>
-
 For more details, see [Activating & Pausing Workflows](/cre/guides/operations/activating-pausing-workflows).
 
 ## `cre workflow pause`