> 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/march-2026/march-11-2026.md).

# March 11, 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:

### PKCE Enabled for All Flow OAuth2 Integrations

All automation OAuth2 credential connections now use Proof Key for Code Exchange (PKCE). PKCE was enabled for the OAuth2 strategy powering Flow connections, which protects authorization-code exchanges against interception attacks. No action is required for existing connected credentials; new connections automatically use PKCE.

Reference: [Automation Integrations](/automations/automation/integrations.md)

***

### Custom Domain SSL: Delegated DCV + Reliability Improvements

Managed custom domain SSL provisioning now uses Cloudflare delegated Domain Control Validation (DCV). Instead of requiring the app owner to add a TXT record per certificate renewal, a single CNAME delegation record handles all future renewals automatically.

Additional reliability improvements shipped alongside this:

* SSL provisioning now uses GET-after-POST verification with Fibonacci backoff to avoid race conditions in Cloudflare hostname activation.
* The domain purchase flow now validates that the Genesis app has been built before allowing a custom domain to be attached, preventing provisioning errors on unpublished apps.

Reference: [Custom Domains](/taskade-genesis/space-apps-guide/custom-domains.md)


---

# 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/march-2026/march-11-2026.md?ask=<question>&goal=<endgoal>
```

`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.