Oracle Enterprise Scheduling Service

Mark a submitted request as deleted

delete

ess/rest/scheduler/v1/requests/{requestId}

Marks a submitted request as deleted. For parent requests, this operation will cascade to all children. The target request must be a submitted request that has finished and is in a terminal state. An error occurs if the target request is not in a terminal state, or if it is a child request of some kind, for example, a JobSet step, a sub-request, or a Schedule instance request. This does not physically remove request data, although the request will no longer be accessible (visible) for most operations.

Request

Path Parameters

requestId(required): integer(int64)

the job request ID

There's no request body for this operation.

Response

Supported Media Types

application/json
application/vnd.oracle.resource+json

204 Response

Request logically deleted

400 Response

Deletion of the request cannot be performed due to the state of the request.

Root Schema : SimpleExceptionDetail

Type: object

Show Source

detail: string

Detailed error message
errorCode: string

ESS-specific error code. For example ESS-00500.
status: integer

HTTP status code
title(required): string

summary error message
type(required): string

URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page.

{
    "required":[
        "title",
        "type"
    ],
    "type":"object",
    "properties":{
        "type":{
            "type":"string",
            "description":"URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page."
        },
        "title":{
            "type":"string",
            "description":"summary error message"
        },
        "status":{
            "type":"integer",
            "description":"HTTP status code"
        },
        "detail":{
            "type":"string",
            "description":"Detailed error message"
        },
        "errorCode":{
            "type":"string",
            "description":"ESS-specific error code. For example ESS-00500."
        }
    }
}

403 Response

Not allowed for this operation

Root Schema : SimpleExceptionDetail

Type: object

Show Source

detail: string

Detailed error message
errorCode: string

ESS-specific error code. For example ESS-00500.
status: integer

HTTP status code
title(required): string

summary error message
type(required): string

URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page.

{
    "required":[
        "title",
        "type"
    ],
    "type":"object",
    "properties":{
        "type":{
            "type":"string",
            "description":"URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page."
        },
        "title":{
            "type":"string",
            "description":"summary error message"
        },
        "status":{
            "type":"integer",
            "description":"HTTP status code"
        },
        "detail":{
            "type":"string",
            "description":"Detailed error message"
        },
        "errorCode":{
            "type":"string",
            "description":"ESS-specific error code. For example ESS-00500."
        }
    }
}

404 Response

Request ID not found

Root Schema : SimpleExceptionDetail

Type: object

Show Source

detail: string

Detailed error message
errorCode: string

ESS-specific error code. For example ESS-00500.
status: integer

HTTP status code
title(required): string

summary error message
type(required): string

URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page.

{
    "required":[
        "title",
        "type"
    ],
    "type":"object",
    "properties":{
        "type":{
            "type":"string",
            "description":"URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page."
        },
        "title":{
            "type":"string",
            "description":"summary error message"
        },
        "status":{
            "type":"integer",
            "description":"HTTP status code"
        },
        "detail":{
            "type":"string",
            "description":"Detailed error message"
        },
        "errorCode":{
            "type":"string",
            "description":"ESS-specific error code. For example ESS-00500."
        }
    }
}

409 Response

Conflict

Root Schema : SimpleExceptionDetail

Type: object

Show Source

detail: string

Detailed error message
errorCode: string

ESS-specific error code. For example ESS-00500.
status: integer

HTTP status code
title(required): string

summary error message
type(required): string

URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page.

{
    "required":[
        "title",
        "type"
    ],
    "type":"object",
    "properties":{
        "type":{
            "type":"string",
            "description":"URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page."
        },
        "title":{
            "type":"string",
            "description":"summary error message"
        },
        "status":{
            "type":"integer",
            "description":"HTTP status code"
        },
        "detail":{
            "type":"string",
            "description":"Detailed error message"
        },
        "errorCode":{
            "type":"string",
            "description":"ESS-specific error code. For example ESS-00500."
        }
    }
}

500 Response

Scheduling sub-system error

Root Schema : SimpleExceptionDetail

Type: object

Show Source

detail: string

Detailed error message
errorCode: string

ESS-specific error code. For example ESS-00500.
status: integer

HTTP status code
title(required): string

summary error message
type(required): string

URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page.

{
    "required":[
        "title",
        "type"
    ],
    "type":"object",
    "properties":{
        "type":{
            "type":"string",
            "description":"URI. It will be beneficial if teams can provide application specific problem types. If not, at least we should link to HTTP error code page."
        },
        "title":{
            "type":"string",
            "description":"summary error message"
        },
        "status":{
            "type":"integer",
            "description":"HTTP status code"
        },
        "detail":{
            "type":"string",
            "description":"Detailed error message"
        },
        "errorCode":{
            "type":"string",
            "description":"ESS-specific error code. For example ESS-00500."
        }
    }
}