Flows v4 API: per-action rate limits are not exposed on GET and are wiped on PUT
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- python
研究方向
Start at the SDK entry points for GET and PUT /automation/v4/flows/{flowId} and the action representation. Determine whether this repository can expose and round-trip rateLimit, or whether the API server must change; done means rate limits survive an unrelated PUT and can be verified through GET, with the limitation documented if not.
由索引模型根據 Issue 內容生成。
描述
Portal 24229793, workflow 1894100404 (contact workflow), Automation API v4.
What happens. The workflow editor lets us set a per-action rate limit on actions such as "Send a webhook" (Configure rate limit, for example 1 execution per 2 seconds). That setting is not present in the GET /automation/v4/flows/{flowId} response: the webhook action object carries method, webhookUrl, queryParams and connection, nothing about rate limiting. A PUT /automation/v4/flows/{flowId} built from that GET response, the documented way to update a flow, therefore saves the workflow without the rate limits, and they are silently removed.
Reproduced on Oct 1, 2026, three times (flow revisions 61, 66 and 68): set the limit in the UI, GET the flow, PUT the same body with an unrelated change, the limit is gone in the UI.
Requests.
- Expose the rate limit on the action object in the GET response, for example
rateLimit: {executions, timeFrameValue, timeFrameUnit}. - Accept it on PUT, or at least preserve it when the PUT body omits it.
- Until then, document that PUT removes action rate limits.
Why it matters. The rate limit protects a downstream SMS provider from webhook bursts. Losing it silently on every API update is a production risk, and today there is no API way to even verify the setting is still there.
Filed here because the gap is in the API the SDK wraps; happy to move it to the right tracker.
- 主要語言
- Python
- 星號
- 437
- 分支
- 127
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
HubSpot/hubspot-api-python 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 65/100
HubSpot/hubspot-api-python#497 ·
-
難度 3/5 1-2 天 新手友好度 58/100
HubSpot/hubspot-api-python#498 · 1 則留言 ·
-
難度 4/5 3-5 天 新手友好度 52/100
HubSpot/hubspot-api-python#496 ·
-
難度 4/5 3-5 天 新手友好度 35/100
HubSpot/hubspot-api-python#495 · 1 則留言 · 2 個 reaction ·
-
難度 4/5 3-5 天 新手友好度 52/100
HubSpot/hubspot-api-python#494 ·
查看 HubSpot/hubspot-api-python 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 86/100
-
Validate finite output clamping limits in StepPredictor.prepare_clamping_params to prevent silent NaN/Inf propagation可能已有人在做 @muskan-creates352 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 84/100
mllam/neural-lam#848 ·
維護者通常 2 天內回覆
-
infra
難度 1/5 1 小時以內 新手友好度 88/100
fab-geocommuns/RNB-coeur#1166 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
deepspeedai/DeepSpeed#8951 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
aws/context-ontology-accelerator#343 ·
維護者通常 1 天內回覆