[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-08-18(UTC)"],[],[],null,["# Retry jobs\n\nBy default, if a Cloud Scheduler job doesn't receive an acknowledgement\nfrom its handler, the job is considered to have failed, and will retry according\nto the exponential backoff you have configured. You can determine this retry\nbehavior in the following ways when creating or updating a\nCloud Scheduler job:\n\n- [Using the Google Cloud console](https://console.cloud.google.com/cloudscheduler)\n\n- [Using the Google Cloud CLI](/sdk/gcloud/reference/scheduler/jobs)\n\n- [Making a direct API request](/scheduler/docs/reference/rest/v1/projects.locations.jobs#retryconfig)\n and configuring the `RetryConfig`settings of a `Job` resource\n\nRetry settings\n--------------\n\nThe following tables describe the retry settings that you can configure.\n\n### Maximum retry attempts\n\nThe number of attempts that the system will make to run a job using the\nexponential backoff procedure described by `maxDoublings`.\n| **Note:** Setting `retryCount` to 0 doesn't prevent failed jobs from running according to schedule after the failure.\n\n### Maximum retry duration\n\nThe time limit for retrying a failed job, measured from the time when an\nexecution was first attempted. If specified with `retryCount`, the job will be\nretried until *both limits are reached*.\n\n### Minimum backoff duration\n\nThe minimum amount of time to wait before retrying a job after it fails.\n\n### Maximum backoff duration\n\nThe maximum amount of time to wait before retrying a job after it fails.\n\n### Maximum doublings\n\nMaximum number of times that the interval between failed job retries will be\ndoubled before the increase becomes constant.\n\nRetry examples\n--------------\n\nThe following examples demonstrate the retry behavior when a\nCloud Scheduler job doesn't complete successfully.\n\nIf both `retryCount` and `maxRetryDuration` are not set\n\n: Both settings default to 0 and the job doesn't retry at all.\n\n Note that Cloud Scheduler will try to run the job at the next\n scheduled execution time.\n\nIf both `retryCount` and `maxRetryDuration` are set\n\n: The job will retry at least `retryCount` number of times until reaching\n `maxRetryDuration`.\n\n Note that the job could retry more times than the `retryCount`.\n\nIf `retryCount` is set and `maxRetryDuration` is not set\n\n: The `maxRetryDuration` setting defaults to 0 and the job will retry exactly\n `retryCount` number of times.\n\nIf `retryCount` is not set and `maxRetryDuration` is set\n\n: The job will retry any number of times (up to a maximum of 5 times) or until\n reaching `maxRetryDuration`."]]
