---
schema_version: "1"
id: 4274023e9b021722fbcf153db4662a9b29993ae0930ed3ddb4cc3f50264e5d91
title: Sub-Actions
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/sfcliplugin/guides/design/sub-actions.md
canonical_url: https://developer.salesforce.com/docs/platform/salesforce-cli-plugin/guide/sub-actions.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: b4a83f49437bd510ed94f76c9651d138f8d43ebdf5abeaf8562caaacc3e954bf
products:
  - Salesforce CLI Plugin Developer Guide
  - salesforcedx
---
# Sub-Actions

Sub-actions are additional verbs that qualify the primary action. Sub-actions are optional and used only when necessary. For example, in the command `sf project deploy start`, the sub-action `start` qualifies what the command `project deploy` does.

A sub-action can also be a followup action related to a previous asynchronous action. For example, `sf data query` with the `--async` flag starts a bulk query. You can then use `sf data query resume --use-most-recent` to "resume" that query at a later time.

## Guidelines

- Sub-actions are optional.
- Sub-actions are verbs.

## Good Examples

- `sf project deploy start` (`start` is the sub-action)
- `sf project deploy preview` (`preview` is the sub-action)
- `sf project deploy report` (`report` is the sub-action)
- `sf data import resume` (`resume` is the sub-action)