Initializing help system before first use

insightapi2~cancel_jobs

Purpose
Cancel all jobs, all jobs owned by the current user, or all jobs for a given scenario. If a provided owner ID matches the current user, all jobs owned by that user will be cancelled. If a scenario ID is provided, the job belonging to that scenario will be cancelled. If neither owner nor scenario ID is provided, all jobs will be cancelled if the current user has sufficient authority to do so.
Synopsis
procedure cancel_jobs(client:insightapi2~insightconfig, req:insightapi2~httprequest, resp:insightapi2~httpresponse)
procedure cancel_jobs(client:insightapi2~insightconfig, owner_id:text, scenario_id:text, resp:insightapi2~httpresponse)
procedure cancel_jobs(client:insightapi2~insightconfig, owner_id:text, scenario_id:text)
Arguments
client 
An initialized insightapi2~insightconfig to call
req 
An initialized insightapi2~httprequest record. The params field may contain these indexes:
ownerId 
The owner ID
scenarioId 
The scenario ID
owner_id 
The owner ID
scenario_id 
The scenario ID
resp 
A insightapi2~httpresponse record into which will be written a description of the response
Further information
1. Use the status field of the resp record to distinguish between different status codes returned by the operation, or the success attribute to check for 2xx status codes. If the resp record is not passed to this procedure, the model will abort with a runtime error if the response's status code does not indicate success. The expected responses from this operation are:
HTTP Status Code Response body type Description
202 The request to cancel the jobs has been accepted
403 The user did not have authority to cancel the jobs, or an owner ID was supplied but it did not match the current user, or a scenario ID was supplied but the user did not have authority for that scenario
404 insightapi2~error_response The scenario did not exist or was unavailable to the current user
429 insightapi2~error_response The jobs were already being cancelled.

2. If the response body could be read into a Mosel variable, it would be written to the body field of the resp record, and the bodyfilename field of the resp record will be an empty string.
3. If the bodyfilename field of the resp record is set to a non-empty value on return, this will be a file containing the response body; the caller is responsible for deleting this file when it is no longer required.
Related topics
insightapi2~error_response
insightapi2~insightconfig
insightapi2~httprequest
insightapi2~httpresponse

Parent Topic Jobs Operations

© 2001-2025 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.