Wenn die im <Rate>-Element der Spike Arrest-Richtlinie angegebene Spitze keine Ganzzahl oder weder ps noch pm als Suffix hat, schlägt die Bereitstellung des API-Proxys fehl.
Gültige Werte sind [int]ps und [int]pm.
Wenn beispielsweise die Spitze beim Versandanstieg als 30.1ps im Element <Rate> einer Spike Arrest-Richtlinie festgelegt ist, dann schlägt die Bereitstellung der API Proxy fehl. Dies liegt daran, dass 30.1 keine Ganzzahl ist.
Diagnose
Identifizieren Sie den ungültigen, in der Spike Arrest-Richtlinie angegebenen Wert.
Diese Information finden Sie in der Fehlermeldung. Im folgenden Fehler ist der ungültige Wert: 30.1
Untersuchen Sie alle Spike Arrest-Richtlinien im entsprechenden API-Proxy, auf dem der Fehler aufgetreten ist. Wenn es eine Spike Arrest-Richtlinie gibt, bei der die im <Rate>-Element angegebene Spitze der in Schritt 1 ermittelten ungültigen Spike Arrest-Rate entspricht, ist dies die Ursache des Fehlers.
Beispiel: Folgende Richtlinie gibt den Wert von <Rate> als 30.1ps an, was mit der Fehlermeldung übereinstimmt:
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-09-04 (UTC)."],[[["\u003cp\u003eThis documentation addresses an error where API proxy deployment fails due to an invalid spike arrest rate specified in the Spike Arrest Policy.\u003c/p\u003e\n"],["\u003cp\u003eThe error, "Invalid spike arrest rate," occurs when the \u003ccode\u003e<Rate>\u003c/code\u003e element within the Spike Arrest Policy is not an integer or lacks the \u003ccode\u003eps\u003c/code\u003e or \u003ccode\u003epm\u003c/code\u003e suffix.\u003c/p\u003e\n"],["\u003cp\u003eDiagnosis involves identifying the invalid rate from the error message and locating the corresponding Spike Arrest policy with the incorrect \u003ccode\u003e<Rate>\u003c/code\u003e value.\u003c/p\u003e\n"],["\u003cp\u003eTo resolve the issue, the \u003ccode\u003e<Rate>\u003c/code\u003e element in the Spike Arrest Policy must be modified to use an integer value with either \u003ccode\u003eps\u003c/code\u003e (per second) or \u003ccode\u003epm\u003c/code\u003e (per minute) as a suffix.\u003c/p\u003e\n"]]],[],null,["# Spike Arrest policy deployment error troubleshooting\n\n*You're viewing **Apigee** and **Apigee hybrid** documentation.\nView [Apigee Edge](https://docs.apigee.com/api-platform/troubleshoot/policies/deployment/spike-arrest-deployment-errors) documentation.*\n| Was this troubleshooting playbook helpful? Please let us know by clicking [Send Feedback]().\n\nInvalidAllowedRate\n------------------\n\n### Error message\n\nDeployment of the API proxy through either the Apigee UI or API fails\nwith this error message: \n\n```transact-sql\nError Saving Revision [revision_number]\nInvalid spike arrest rate [invalid_rate].\n```\n\n**Example error messages** \n\n Error Saving Revision 1\n Invalid spike arrest rate 30s.\n\n Error Saving Revision 1\n Invalid spike arrest rate 30.1ps.\n\n**Example screenshots**\n\n### Cause\n\nIf the spike arrest rate specified in the `\u003cRate\u003e` element of the Spike Arrest\nPolicy is not an integer or if the rate does not have `ps` or `pm` as a suffix,\nthen the deployment of the API proxy fails.\n\nThe valid values are `[`***int***`]ps` and `[`***int***`]pm`.\n\nFor example, if the spike arrest rate specified is `30.1ps` in the `\u003cRate\u003e` element\nof a Spike Arrest Policy, then the deployment of the API proxy fails. This is\nbecause 30.1 is not an integer.\n\n### Diagnosis\n\n1. Identify the invalid spike arrest rate specified in the Spike Arrest policy.\n You can find this information from the error message. For example, in the following\n error, the invalid spike arrest is `30.1`:\n\n Error Saving Revision 1\n Invalid spike arrest rate 30.1ps.\n\n2. Examine all the Spike Arrest policies in the specific API proxy where the\n failure has occurred. If there is any Spike Arrest policy in which the spike\n arrest specified in the `\u003cRate\u003e` element matches the invalid spike arrest rate\n identified in Step #1 above, then that's the cause of the error.\n\n For example, the following policy specifies the value of `\u003cRate\u003e` as 30.1ps,\n which matches what's in the error message: \n\n \u003c?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?\u003e\n \u003cSpikeArrest async=\"false\" continueOnError=\"false\" enabled=\"true\" name=\"CheckRate\"\u003e\n \u003cDisplayName\u003eCheckRate\u003c/DisplayName\u003e\n \u003cProperties/\u003e\n \u003cIdentifier ref=\"request.header.some-header-name\"/\u003e\n \u003cMessageWeight ref=\"request.header.weight\"/\u003e\n \u003cRate\u003e30.1ps\u003c/Rate\u003e\n \u003c/SpikeArrest\u003e\n\n Since the spike arrest rate specified in the `\u003cRate\u003e` element is not an integer,\n the deployment of the API Proxy fails with the error: \n\n Invalid spike arrest rate 30.1ps.\n\n### Resolution\n\nEnsure that the value of the spike arrest rate specified in the `\u003cRate\u003e` element\nof the Spike Arrest Policy is an integer and has `ps` or `pm` as a suffix. For\nexample: \n\n \u003c?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?\u003e\n \u003cSpikeArrest async=\"false\" continueOnError=\"false\" enabled=\"true\" name=\"CheckRate\"\u003e\n \u003cDisplayName\u003eCheckRate\u003c/DisplayName\u003e\n \u003cProperties/\u003e\n \u003cIdentifier ref=\"request.header.some-header-name\"/\u003e\n \u003cMessageWeight ref=\"request.header.weight\"/\u003e\n \u003cRate\u003e30ps\u003c/Rate\u003e\n \u003c/SpikeArrest\u003e"]]
