BatchClient.JobScheduleExistsAsync Method

Reference

Definition

Namespace:: Azure.Compute.Batch

Assembly:: Azure.Compute.Batch.dll

Package:: Azure.Compute.Batch v1.0.0-beta.1

Source:: BatchClientCustom.cs

Important

Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

[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 System.Threading.Tasks.Task<Azure.Response<bool>> JobScheduleExistsAsync (string jobScheduleId, int? timeOut = default, DateTimeOffset? ocpDate = default, Azure.RequestConditions requestConditions = default, Azure.RequestContext context = default);

abstract member JobScheduleExistsAsync : string * Nullable<int> * Nullable<DateTimeOffset> * Azure.RequestConditions * Azure.RequestContext -> System.Threading.Tasks.Task<Azure.Response<bool>>
override this.JobScheduleExistsAsync : string * Nullable<int> * Nullable<DateTimeOffset> * Azure.RequestConditions * Azure.RequestContext -> System.Threading.Tasks.Task<Azure.Response<bool>>

Public Overridable Function JobScheduleExistsAsync (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 Task(Of 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.