Skip to content

chore: update bulk resume command examples #1277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mdonnalley merged 2 commits into from
Jul 7, 2025
Merged

chore: update bulk resume command examples #1277

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1243173
chore: update data.export.resume.md
cristiand391 Jul 7, 2025
456d70f
Update data.update.resume.md
cristiand391 Jul 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions messages/data.export.resume.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ Resume a bulk export job that you previously started. Uses Bulk API 2.0.

When the original "data export bulk" command either times out or is run with the --async flag, it displays a job ID. To see the status and get the results of the bulk export, run this command by either passing it the job ID or using the --use-most-recent flag to specify the most recent bulk export job.

Using either `--job-id` or `--use-most-recent` will properly resolve to the correct org where the bulk job was started based on the cached data by "data export bulk".

# flags.job-id.summary

Job ID of the bulk export.
Expand All @@ -16,10 +18,10 @@ Use the job ID of the bulk export job that was most recently run.

# examples

- Resume a bulk export job run on your default org by specifying a job ID:
- Resume a bulk export job run by specifying a job ID:

sf <%= command.id %> --job-id 750xx000000005sAAA

- Resume the most recently-run bulk export job for an org with alias my-scratch:
- Resume the most recently-run bulk export job:

sf data export resume --use-most-recent --target-org my-scratch
sf data export resume --use-most-recent
8 changes: 5 additions & 3 deletions messages/data.update.resume.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,17 @@ Resume a bulk update job that you previously started. Uses Bulk API 2.0.

When the original "sf data update bulk" command either times out or is run with the --async flag, it displays a job ID. To see the status and get the results of the bulk update, run this command by either passing it the job ID or using the --use-most-recent flag to specify the most recent bulk update job.

Using either `--job-id` or `--use-most-recent` will properly resolve to the correct org where the bulk job was started based on the cached data by "data update bulk".

# examples

- Resume a bulk update job of your default org using a job ID:
- Resume a bulk update job using a job ID:

<%= config.bin %> <%= command.id %> --job-id 750xx000000005sAAA

- Resume the most recently run bulk update job for an org with alias "my-scratch":
- Resume the most recently run bulk update job:

<%= config.bin %> <%= command.id %> --use-most-recent --target-org my-scratch
<%= config.bin %> <%= command.id %> --use-most-recent

# flags.use-most-recent.summary

Expand Down
Loading