Skip to content

Commit e106be4

Browse files
Update fhir-bulk-delete-operation.md - make FAQs bulleted
1 parent c9e4e4e commit e106be4

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

articles/healthcare-apis/includes/fhir-bulk-delete-operation.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -111,13 +111,9 @@ Here's a list of error messages that might occur if the `$bulk-delete` operation
111111
112112
## FAQ
113113
114-
1. My `$bulk-delete` job seems to be stuck. What are the steps for resolution?
114+
- My `$bulk-delete` job seems to be stuck. What are the steps for resolution?<br/><br/> To check if a `$bulk-delete` job is stuck, run a FHIR search with the same parameters as the bulk delete job and _summary=count. If the count of resources is going down, the job is working. You can also cancel the `$bulk-delete` job and try again.
115115
116-
To check if a `$bulk-delete` job is stuck, run a FHIR search with the same parameters as the bulk delete job and _summary=count. If the count of resources is going down, the job is working. You can also cancel the `$bulk-delete` job and try again.
117-
118-
1. Do API interactions see any latency impact when a `$bulk-delete` operation job is executed concurrently?
119-
120-
When you run a `$bulk-delete` operation, you might see increased latency on concurrent calls to the service. To avoid a latency increase, we recommend that you cancel the `$bulk-delete` job, and then rerun it during a period of lower traffic.
116+
- Do API interactions see any latency impact when a `$bulk-delete` operation job is executed concurrently?<br/><br/>When you run a `$bulk-delete` operation, you might see increased latency on concurrent calls to the service. To avoid a latency increase, we recommend that you cancel the `$bulk-delete` job, and then rerun it during a period of lower traffic.
121117
122118
> [!NOTE]
123119
> If you cancel and then restart a `$bulk-delete` operation, the deletion process resumes from where it was stopped.

0 commit comments

Comments
 (0)