@@ -115,257 +115,3 @@ The following example shows the response.
115115``` http
116116HTTP/1.1 204 No Content
117117```
118-
119- ### Example 2: Workflow not found
120-
121- The following example shows a request where the specified workflow doesn't exist.
122-
123- #### Request
124-
125- The following example shows a request.
126-
127- <!-- {
128- "blockType": "request",
129- "name": "lifecycleworkflows_workflow_cancelprocessing_workflownotfound"
130- }
131- -->
132- ``` http
133- POST https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/00000000-0000-0000-0000-000000000000/cancelProcessing
134- Content-Type: application/json
135-
136- {
137- "scope": {
138- "@odata.type": "#microsoft.graph.identityGovernance.cancelRunsScope",
139- "runs": [
140- {
141- "id": "8cdf25a8-c9d2-423e-a03d-3f39f03c3e97"
142- }
143- ]
144- }
145- }
146- ```
147-
148- #### Response
149-
150- The following example shows the response.
151-
152- <!-- {
153- "blockType": "response",
154- "truncated": true
155- } -->
156- ``` http
157- HTTP/1.1 404 Not Found
158- Content-Type: application/json
159-
160- {
161- "error": {
162- "code": "Resource not found",
163- "message": "Workflow with id '00000000-0000-0000-0000-000000000000' was not found."
164- }
165- }
166- ```
167-
168- ### Example 3: No valid runs provided
169-
170- The following example shows a request where no valid run IDs are provided. An error is returned when a request contains zero valid runs, either from an empty runs array or only invalid run IDs.
171-
172- #### Request
173-
174- The following example shows a request.
175-
176- <!-- {
177- "blockType": "request",
178- "name": "lifecycleworkflows_workflow_cancelprocessing_novalid"
179- }
180- -->
181- ``` http
182- POST https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/14879e66-9ea9-48d0-804d-8fea672d0341/cancelProcessing
183- Content-Type: application/json
184-
185- {
186- "scope": {
187- "@odata.type": "#microsoft.graph.identityGovernance.cancelRunsScope",
188- "runs": [
189- {
190- "id": "00000000-0000-0000-0000-000000000001"
191- },
192- {
193- "id": "00000000-0000-0000-0000-000000000002"
194- }
195- ]
196- }
197- }
198- ```
199-
200- #### Response
201-
202- The following example shows the response.
203-
204- <!-- {
205- "blockType": "response",
206- "truncated": true
207- } -->
208- ``` http
209- HTTP/1.1 406 Not Acceptable
210- Content-Type: application/json
211-
212- {
213- "error": {
214- "code": "Not Acceptable Request",
215- "message": "No valid runs in cancelRunsScope supplied. 2 runs were specified and none were valid."
216- }
217- }
218- ```
219-
220- ### Example 4: Run doesn't belong to workflow
221-
222- The following example shows a request where the provided run doesn't belong to the specified workflow.
223-
224- #### Request
225-
226- The following example shows a request.
227-
228- <!-- {
229- "blockType": "request",
230- "name": "lifecycleworkflows_workflow_cancelprocessing_wrongworkflow"
231- }
232- -->
233- ``` http
234- POST https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/14879e66-9ea9-48d0-804d-8fea672d0341/cancelProcessing
235- Content-Type: application/json
236-
237- {
238- "scope": {
239- "@odata.type": "#microsoft.graph.identityGovernance.cancelRunsScope",
240- "runs": [
241- {
242- "id": "8cdf25a8-c9d2-423e-a03d-3f39f03c3e97"
243- }
244- ]
245- }
246- }
247- ```
248-
249- #### Response
250-
251- The following example shows the response.
252-
253- <!-- {
254- "blockType": "response",
255- "truncated": true
256- } -->
257- ``` http
258- HTTP/1.1 400 Bad Request
259- Content-Type: application/json
260-
261- {
262- "error": {
263- "code": "Bad Request",
264- "message": "Run with id '8cdf25a8-c9d2-423e-a03d-3f39f03c3e97' does not belong to workflow '14879e66-9ea9-48d0-804d-8fea672d0341'."
265- }
266- }
267- ```
268-
269- ### Example 5: Run not in cancelable state
270-
271- The following example shows a request where the run isn't in a cancelable state. Only runs with status ` queued ` or ` inProgress ` can be canceled.
272-
273- #### Request
274-
275- The following example shows a request.
276-
277- <!-- {
278- "blockType": "request",
279- "name": "lifecycleworkflows_workflow_cancelprocessing_notcancellable"
280- }
281- -->
282- ``` http
283- POST https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/14879e66-9ea9-48d0-804d-8fea672d0341/cancelProcessing
284- Content-Type: application/json
285-
286- {
287- "scope": {
288- "@odata.type": "#microsoft.graph.identityGovernance.cancelRunsScope",
289- "runs": [
290- {
291- "id": "8cdf25a8-c9d2-423e-a03d-3f39f03c3e97"
292- }
293- ]
294- }
295- }
296- ```
297-
298- #### Response
299-
300- The following example shows the response.
301-
302- <!-- {
303- "blockType": "response",
304- "truncated": true
305- } -->
306- ``` http
307- HTTP/1.1 409 Conflict
308- Content-Type: application/json
309-
310- {
311- "error": {
312- "code": "Conflict",
313- "message": "Run with id '8cdf25a8-c9d2-423e-a03d-3f39f03c3e97' is not in a cancellable state. Current status: 'completed'. Must be 'queued' or 'in-progress' to cancel."
314- }
315- }
316- ```
317-
318- ### Example 6: Too many runs
319-
320- The following example shows a request that exceeds the maximum number of runs allowed per request. Currently, only one run can be canceled per request.
321-
322- #### Request
323-
324- The following example shows a request.
325-
326- <!-- {
327- "blockType": "request",
328- "name": "lifecycleworkflows_workflow_cancelprocessing_toomany"
329- }
330- -->
331- ``` http
332- POST https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/14879e66-9ea9-48d0-804d-8fea672d0341/cancelProcessing
333- Content-Type: application/json
334-
335- {
336- "scope": {
337- "@odata.type": "#microsoft.graph.identityGovernance.cancelRunsScope",
338- "runs": [
339- {
340- "id": "8cdf25a8-c9d2-423e-a03d-3f39f03c3e97"
341- },
342- {
343- "id": "2b08131a-8083-450d-9a1f-2aecb406a6f4"
344- },
345- {
346- "id": "e7904bb5-df48-48ee-a0e1-264d5c121355"
347- }
348- ]
349- }
350- }
351- ```
352-
353- #### Response
354-
355- The following example shows the response.
356-
357- <!-- {
358- "blockType": "response",
359- "truncated": true
360- } -->
361- ``` http
362- HTTP/1.1 400 Bad Request
363- Content-Type: application/json
364-
365- {
366- "error": {
367- "code": "Bad Request",
368- "message": "Too many runs provided. Received 3, but the maximum allowed in a single cancelProcessing call is 1."
369- }
370- }
371- ```
0 commit comments