Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Batas Layanan Saluran
Tabel di bawah mencantumkan beberapa batasan yang berlaku untuk Layanan Channel
Batas resource
Resource
Batas
Akun
1 per domain reseller
Pelanggan
Tidak terbatas
Hak
Tidak terbatas
Link Partner Saluran
Tidak terbatas
Batas Google Workspace
Resource
Batas
Jumlah kursi maksimum
50.000 (hubungi Dukungan untuk menambah)
Durasi uji coba maksimum
30 hari (untuk SKU yang berlaku)
Batas khusus untuk Partner Sales Console Pengujian
Resource
Batas
Jumlah kursi maksimum
10
Durasi uji coba maksimum
1 hari
Ada pertimbangan tambahan saat menggunakan Partner Sales Console Pengujian:
Pelanggan harus mengikuti konvensi penamaan domain pengujian.
Hak Google Workspace ditandai untuk dihapus 3 hari setelah pembuatan, dan dihapus setiap minggu.
Batas kapasitas Cloud Channel API
Batas kapasitas API menentukan jumlah permintaan yang dapat dibuat ke Cloud Channel API. Batas ada berdasarkan per project dan semua permintaan API,
termasuk permintaan yang tidak valid, akan dikenai biaya kuota.
Batas kapasitas diterapkan dengan interval 60 detik (1 menit). Jika mencapai batas dalam waktu 60 detik, Anda harus menunggu kuota diperbarui untuk membuat lebih banyak permintaan.
Kami memiliki bucket kuota yang berbeda untuk grup endpoint yang berbeda. Penggunaan kuota
di setiap bucket dievaluasi secara terpisah. Tabel berikut mencantumkan batas kuota Cloud Channel API per project spesifik dan default, serta metode yang berlaku.
Jika memerlukan batas kapasitas yang lebih tinggi untuk permintaan API, Anda dapat meminta peningkatan melalui konsolGoogle Cloud .
Praktik terbaik
Berikut beberapa praktik terbaik untuk membantu Anda mengatasi batas kapasitas API di
Cloud Channel API.
Gunakan pembatasan kapasitas sisi klien untuk menetapkan batas kapasitas buatan.
Hal ini dapat mencegah satu klien menggunakan semua kuota Anda.
Gunakan
backoff eksponensial
untuk memberi jarak permintaan secara bertahap setelah Anda mencapai kuota. Tindakan ini memberi
server waktu untuk mengisi ulang bucket Anda.
Ikuti rekomendasi polling yang dijelaskan untuk semua metode yang menampilkan Operasi saat memanggil operations.get
Jika Anda menerima error 403 dengan pesan rateLimitExceeded, tunggu
beberapa detik, lalu coba lagi permintaan Anda. Kuota diisi ulang setiap 60
detik, sehingga permintaan Anda akan berhasil setelah menunggu pembaruan berikutnya.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[[["\u003cp\u003eChannel Services has resource limits, including one account per reseller domain, unlimited customers, entitlements, and channel partner links.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Workspace seat limits are set at 50,000, with the possibility to contact support for an increase, and trial durations are limited to 30 days for applicable SKUs.\u003c/p\u003e\n"],["\u003cp\u003eThe Test Partner Sales Console has a limit of 10 seats and a 1-day trial duration, with test domain naming convention and Google Workspace entitlements marked for deletion.\u003c/p\u003e\n"],["\u003cp\u003eCloud Channel API rate limits are enforced at 60-second intervals, with varying request limits per minute depending on the specific API method, and an overall limit of 120 for all other endpoints.\u003c/p\u003e\n"],["\u003cp\u003eBest practices for managing API rate limits include using a client-side rate limiter, implementing exponential backoff, following polling recommendations for \u003ccode\u003eoperations.get\u003c/code\u003e, and waiting a few seconds to retry after a \u003ccode\u003erateLimitExceeded\u003c/code\u003e error.\u003c/p\u003e\n"]]],[],null,["# Quotas & limits\n\nChannel Services limits\n-----------------------\n\nThe table below lists several limits applying to Channel Services\n\n### Resources limits\n\n### Google Workspace limits\n\n#### Limits specific to Test Partner Sales Console\n\nThere are additional considerations when using a Test Partner Sales Console:\n\n- Customers need to follow the test domain naming convention.\n- Google Workspace entitlements are marked for deletion 3 days after creation, and deleted weekly.\n\nCloud Channel API rate limits\n-----------------------------\n\nAPI rate limits define the number of requests that can be made to the\nCloud Channel API. Limits exist on a per-project basis and all API requests,\nincluding invalid requests, incur a quota cost.\n\nRate limits are enforced at **60 second (1 minute)** intervals. If you reach\nyour limit within 60 seconds, you need to wait for your quotas to refresh to\nmake more requests.\n\nWe have different quota buckets for different groups of endpoints. Quota usages\nin each bucket are evaluated independently. The following table lists the\nspecific and default per-project Cloud Channel API quota limits, and the\nmethods to which they apply.\n\nIf you need a higher rate limit for API requests, you can request an increase\nvia the\n[Google Cloud console](https://console.cloud.google.com/iam-admin/quotas).\n\n### Best practices\n\nHere are some best practices to help you with the API rate limits on\nCloud Channel API.\n\n- Use a client-side rate limiter to set an artificial rate limit.\n This can keep one client from using all of your quotas.\n\n- Use\n [exponential backoff](https://wikipedia.org/wiki/Exponential_backoff)\n to progressively space out requests once you reach your quota. This gives the\n server time to refill your buckets.\n\n- Follow polling recommendations described for all methods returning an\n Operation when calling `operations.get`\n\n- If you receive a 403 error with the message `rateLimitExceeded`, wait a\n few seconds and try your request again. Quotas are refilled every 60\n seconds, so your request should succeed after waiting for the next refresh."]]
