Deleting Workflows

Deleting a workflow permanently removes it from the registry selected by deployment-registry. This action cannot be undone, and the workflow will no longer be able to respond to triggers.

Prerequisites

Before deleting a workflow, ensure you have:

• A deployed workflow: The workflow must exist in the registry selected by deployment-registry.
• Workflow authorization: You must be authorized to manage the workflow. Public onchain registry workflows use the linked workflow owner address. Private registry workflows use your CRE organization login session.
• Local workflow folder: You must run this command from your project directory. The CLI reads the workflow name and configuration from your workflow.yaml file to identify which workflow to delete.
• Logged in: Authenticated with the platform by running cre login. To check if you are logged in, run cre whoami.
• A deployment-registry value: Updated CLI-generated targets use private by default. For older workflow files, make sure the target has deployment-registry: "private" or deployment-registry: "onchain:ethereum-mainnet".
• (Onchain registry only) A funded wallet: The account must be funded with ETH on Ethereum Mainnet to pay gas for the registry transaction.

Deleting a workflow

To delete a workflow, run the cre workflow delete command from your project root:

cre workflow delete my-workflow --target production-settings

The CLI identifies which workflow to delete based on:

• workflow-name from your workflow.yaml file
• deployment-registry from your workflow.yaml file
• workflow-owner-address for onchain registry workflows, or your CRE organization for private registry workflows

What happens during deletion

1. The CLI fetches all workflows matching your workflow name and configured registry authorization
2. It displays details about the workflow(s) to be deleted
3. It prompts you to confirm by typing the workflow name
4. Once confirmed, it deletes the workflow from the target's configured registry. For onchain:ethereum-mainnet, this sends an onchain transaction. For private, this updates the Chainlink-hosted private registry through your CRE login session.

Example onchain registry output

> cre workflow delete my-workflow --target production-settings

Deleting Workflow :      my-workflow
Target :                 production-settings
Owner Address :          <your-owner-address>

Found 1 workflow(s) to delete for name: my-workflow
   1. Workflow
      ID:              00f0379a2df46ad2c5af070f5871da89f589f8bff8af76ff6a44bb59bec88bf4
      Owner:           <your-owner-address>
      DON Family:      zone-a
      Tag:             my-workflow
      Binary URL:      https://storage.cre.example.com/artifacts/00f0379a.../binary.wasm
      Workflow Status: PAUSED

Are you sure you want to delete the workflow 'my-workflow'?
This action cannot be undone.

To confirm, type the workflow name: my-workflow: my-workflow
Deleting 1 workflow(s)...
Transaction details:
  Chain Name:   ethereum-testnet-sepolia
  To:           0xF3f93fc4dc177748E7557568b5354cB009e3818a
  Function:     DeleteWorkflow
  Inputs:
    [0]:        0x00f0379a2df46ad2c5af070f5871da89f589f8bff8af76ff6a44bb59bec88bf4
  Data:         695e134000f0379a2df46ad2c5af070f5871da89f589f8bff8af76ff6a44bb59bec88bf4
Estimated Cost:
  Gas Price:      0.00100001 gwei
  Total Cost:     0.00000015 ETH
? Do you want to execute this transaction?:
  ▸ Yes
    No

✓ Transaction confirmed
View on explorer: https://sepolia.etherscan.io/tx/0xf059c32...fec7d
✓ Deleted workflow ID: 00f0379a2df46ad2c5af070f5871da89f589f8bff8af76ff6a44bb59bec88bf4
✓ Workflows deleted successfully

Skipping the confirmation prompt

If you want to skip the interactive confirmation prompt (e.g., in automated scripts), use the --yes flag:

cre workflow delete my-workflow --yes --target production-settings

Using multi-sig wallets

For onchain registry workflows, the delete command supports multi-sig wallets through the --unsigned flag. When using this flag, the CLI generates raw transaction data that you can submit through your multi-sig wallet interface instead of sending the transaction directly. Private registry workflows do not use --unsigned because they do not submit registry transactions.

For complete setup instructions, configuration requirements, and step-by-step guidance, see Using Multi-sig Wallets.

Learn more

• Deploying Workflows — Deploy new workflows to the registry
• Activating & Pausing Workflows — Control workflow execution state
• Updating Deployed Workflows — Update existing workflows