Reference documentation and code samples for the Vertex AI v1beta1 API enum Scheduling.Types.Strategy.
Optional. This determines which type of scheduling strategy to use. Right
now users have two options such as STANDARD which will use regular on
demand resources to schedule the job, the other is SPOT which would
leverage spot resources alongwith regular resources to schedule
the job.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eScheduling.Types.Strategy\u003c/code\u003e enum in the Vertex AI v1beta1 API defines how resources are provisioned for a job.\u003c/p\u003e\n"],["\u003cp\u003eThe enum offers options like \u003ccode\u003eStandard\u003c/code\u003e for regular on-demand resources and \u003ccode\u003eSpot\u003c/code\u003e for using spot resources.\u003c/p\u003e\n"],["\u003cp\u003eOther fields are also available, such as \u003ccode\u003eFlexStart\u003c/code\u003e, which uses DWS to queue for resources, and the \u003ccode\u003eUnspecified\u003c/code\u003e field defaults to \u003ccode\u003eStandard\u003c/code\u003e provisioning.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eOnDemand\u003c/code\u003e and \u003ccode\u003eLowCost\u003c/code\u003e are deprecated, which were originally for regular on-demand provisioning and making potential use of spot resources, respectively.\u003c/p\u003e\n"]]],[],null,[]]
