Cloud Scheduler uses quotas and system limits to maintain fair resource
allocation, prevent service overloads, and help you manage resource use.

Quotas and system limits are similar but differ in the following ways:

- *Quotas* have default values, but you can typically request adjustments.
- *System limits* are fixed values that can't be changed.

Google Cloud uses quotas to help maintain fairness and reduce
spikes in resource use and availability. A quota restricts how much of a
Google Cloud resource your Google Cloud project can use. Quotas
apply to a range of resource types, including hardware, software, and network
components. For example, quotas can restrict the number of API calls to a
service, the number of load balancers used concurrently by your project, or the
number of projects that you can create. Quotas protect the community of
Google Cloud users by preventing the overloading of services. Quotas also
help you to manage your own Google Cloud resources.

The Cloud Quotas system does the following:

- Monitors your consumption of Google Cloud products and services
- Restricts your consumption of those resources
- Provides a way to [request changes to the quota value](https://docs.cloud.google.com/docs/quotas/help/request_increase) and [automate quota adjustments](https://docs.cloud.google.com/docs/quotas/quota-adjuster.md.txt)

In most cases, when you attempt to consume more of a resource than its quota
allows, the system blocks access to the resource, and the task that
you're trying to perform fails.

Quotas generally apply at the Google Cloud project
level. Your use of a resource in one project doesn't affect
your available quota in another project. Within a Google Cloud project, quotas
are shared across all applications and IP addresses.


For more information, see the
[Cloud Quotas overview](https://docs.cloud.google.com/docs/quotas/overview.md.txt).


There are also *system limits* on Cloud Scheduler resources.
System limits can't be changed.

## Quotas

Cloud Scheduler enforces the following quotas by default for each
Google Cloud **project** . You can
[increase or decrease these quotas](https://docs.cloud.google.com/scheduler/quotas.md.txt#quota-request):

| Resource | Value |
|---|---|
| Read API requests per minute (including `ListJobs`, `GetJob`, `ListLocations`, and `GetLocation`) | 1,250 |
| Write API requests per minute (including `CreateJob`, `UpdateJob`, `DeleteJob`, `PauseJob`, `ResumeJob`, and `RunJob`) | 500 |
| Number of jobs (per region) | 5,000 |
| Fixed maximum job size (payload) | 1 MB total including \~1 KB request overhead |

## Limits

Cloud Scheduler enforces the following usage limits. You can't request
changes to these limits:

| Limit | Description | Value |
|---|---|---|
| Job duration | The maximum duration (from start time to end time) that Cloud Scheduler waits for a job execution attempt to respond. Any job attempts that exceed the configured [`attemptDeadline`](https://docs.cloud.google.com/scheduler/docs/reference/rest/v1/projects.locations.jobs.md.txt#Job.FIELDS.attempt_deadline) end with a `DEADLINE_EXCEEDED` timeout error and are retried according to the configured [retry policy](https://docs.cloud.google.com/scheduler/docs/configuring/retry-jobs.md.txt): - For HTTP targets, the default deadline is 3 minutes, and you can configure a deadline from 15 seconds to 30 minutes (1,800 seconds). - For App Engine HTTP targets, the default and maximum deadline depends on the service's scaling type: 10 minutes for standard environment automatic scaling, 24 hours for standard environment basic or manual scaling, and 60 minutes for the flexible environment (configurable from 15 seconds up to the scaling type's maximum timeout). - For Pub/Sub targets, `attemptDeadline` is ignored. | - HTTP targets: 30 minutes (1,800 seconds) - App Engine targets: up to 24 hours |

## Requesting a quota increase or decrease

To adjust most quotas, use the Google Cloud console.
For more information, see
[Request a quota adjustment](https://docs.cloud.google.com/docs/quotas/help/request_increase).