BatchClient.JobScheduleExists Method

Definition

[Protocol Method] Checks the specified Job Schedule exists.

  • This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
public virtual Azure.Response<bool> JobScheduleExists (string jobScheduleId, int? timeOut = default, DateTimeOffset? ocpDate = default, Azure.RequestConditions requestConditions = default, Azure.RequestContext context = default);
abstract member JobScheduleExists : string * Nullable<int> * Nullable<DateTimeOffset> * Azure.RequestConditions * Azure.RequestContext -> Azure.Response<bool>
override this.JobScheduleExists : string * Nullable<int> * Nullable<DateTimeOffset> * Azure.RequestConditions * Azure.RequestContext -> Azure.Response<bool>
Public Overridable Function JobScheduleExists (jobScheduleId As String, Optional timeOut As Nullable(Of Integer) = Nothing, Optional ocpDate As Nullable(Of DateTimeOffset) = Nothing, Optional requestConditions As RequestConditions = Nothing, Optional context As RequestContext = Nothing) As Response(Of Boolean)

Parameters

jobScheduleId
String

The ID of the Job Schedule which you want to check.

timeOut
Nullable<Int32>

The maximum number of items to return in the response. A maximum of 1000 applications can be returned.

ocpDate
Nullable<DateTimeOffset>

The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly.

requestConditions
RequestConditions

The content to send as the request conditions of the request.

context
RequestContext

The request context, which can override default behaviors of the client pipeline on a per-call basis.

Returns

The response returned from the service.

Exceptions

jobScheduleId is null.

jobScheduleId is an empty string, and was expected to be non-empty.

Service returned a non-success status code.

Applies to