PrivateCloudComputeLanguageModel returns rateLimited immediately while availability is available and quota is belowLimit

Hello Apple engineers and developers,

I am testing PrivateCloudComputeLanguageModel in an iOS reading app.

Environment:

  • Device: iPhone 16e purchased outside mainland China
  • OS: iOS 27.0.1 (24A446)
  • Our developer team has been approved for PCC access.
  • The app signature and embedded provisioning profile both contain:
    com.apple.developer.private-cloud-compute = true

The app makes one short, foreground, non-streaming request without automatic retry or structured generation:

“Translate this sentence into Simplified Chinese: The stars are beautiful tonight. Return only the translation.”

Immediately before the request:

  • model availability: .available
  • quotaUsage.status: .belowLimit
  • isApproachingLimit: false
  • isLimitReached: false
  • resetDate: nil

Nevertheless, the request fails after approximately 0.11–0.14 seconds with:

FoundationModels.LanguageModelError.rateLimited

No response content is generated. The error does not provide a reset time or additional metadata.

I tested both Apple Development and Ad Hoc builds. Both resulted in the same rate-limit message in the app UI. Changing the app’s bundle identifier did not change the result. Enabling a VPN also did not change the displayed message; I did not verify whether PCC traffic was routed through the VPN.

On October 13, 2026, at approximately 19:04 China Standard Time (UTC+8), I also ran Apple’s Shortcuts app on the same iPhone and selected “Use Model” with Cloud. It showed “Too many requests. Please try again later.” and generated no response.

I repeated the test after switching the device’s primary iCloud account to an account configured for the US region. The device was physically located in mainland China during these tests.

Could you please clarify:

  1. Can account, region, device, or service-side eligibility restrictions appear as rateLimited even when the model reports .available and quotaUsage reports .belowLimit?
  2. Is any additional activation or allowlisting required beyond PCC team approval and the signed entitlement?
  3. Which logs or diagnostics can identify the cause or retry time when resetDate is nil?
  4. Is the Shortcuts Cloud result useful evidence of a device- or account-level restriction, or does Shortcuts use an independent service policy?

Thank you.

Can account, region, device, or service-side eligibility restrictions appear as rateLimited even when the model reports .available and quotaUsage reports .belowLimit?

.rateLimited is an error different from .quotaLimitReached. It can happen when you make too many requests in a short window, even your quota usage is still below the usage limit.

When you use the Foundation Models framework + PCC and get a .rateLimited error, I'd expect that the error info (LanguageModelError.RateLimited) conveys a reset date (resetDate) so you know when to retry. If you see otherwise with the latest beta (now 27.2 RC), I’d suggest that file a feedback report, and share your report ID here..

Is any additional activation or allowlisting required beyond PCC team approval and the signed entitlement?

In case you can add the "Access to models on Private Cloud Compute" capability to your project in Xcode, your app should be able to use PCC.

Note though that Apple Intelligence, and hence PCC, is not available in some regions. For testing purpose, you might want to use an Apple ID and a device that are from a region that has Apple Intelligence.

Which logs or diagnostics can identify the cause or retry time when resetDate is nil?

I'd suggest that you try with 27.2 RC first. If the issue is still there, capture a sysdiagnose from your device, and use it to file a feedback report. See the instructions here, if needed.

Is the Shortcuts Cloud result useful evidence of a device- or account-level restriction, or does Shortcuts use an independent service policy?

It isn't a surprise to me that a system app hits .rateLimited as well, but if you don't really "make too many requests in a short window" when the error happens, meaning the system may wrongly report .rateLimited, I'd again suggest that you file a feedback report with the details of how you trigger the error.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.