> For the complete documentation index, see [llms.txt](https://docs.taskade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskade.com/changelog/changelog-2026/february-2026/february-18-2026.md). # February 18, 2026 {% hint style="info" %} **Developer highlights.** This section tracks API, MCP, SDK, automation, and Taskade Genesis platform changes for developers. For the full product changelog see [taskade.com/changelog](https://www.taskade.com/changelog); for release newsletters see [taskade.com/blog/updates](https://www.taskade.com/blog/updates). {% endhint %} ## What's New: ### Automation: Retry-After Header Support for 429 Responses The automation workflow engine now reads the `Retry-After` header from upstream HTTP 429 responses and schedules the next retry at the time the external service requests, rather than using a fixed back-off interval. Both numeric-seconds (`Retry-After: 60`) and HTTP-date (`Retry-After: Wed, 18 Feb 2026 20:00:00 GMT`) formats are parsed. This improves reliability for automations that call rate-limited external APIs (Shopify, Slack, etc.) without requiring any configuration change on your end. *** ### Automation: Flow-Enable Idempotency Enabling an automation flow (`flowEnable`) is now idempotent — calling it when the flow is already active no longer throws an error. This removes a class of race conditions for integrations that programmatically toggle flows (e.g., via webhook-driven enable/disable cycles). *** ### Automation: Null-Byte Sanitization for Run Records Automation run payloads are now sanitized before being persisted to the automation run store. Null bytes (`\x00`) embedded in webhook or external-API payloads previously caused silent write failures; they are now stripped at ingestion, preventing lost run records. *(items 2–3 shipped February 17)* See [Automation Actions](/automations/automation/actions.md) for the full action library. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.taskade.com/changelog/changelog-2026/february-2026/february-18-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.