> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/release-notes/2026/march-30th-2026.md).

# March 30

We’ve rolled out updates to make the platform faster, more reliable, and easier to understand and use.

## Platform Stability & Performance

* **Better Handling of High Traffic** - Platform stays stable even when many users are active.
  * Requests are queued during peak load
  * Clear messages when systems are busy
* **More Reliable AI Providers** - Less disruption due to model outages.
  * Vertex AI as primary provider
  * Google AI Studio as fallback
* **Improved Publish Experience** - No more confusion when publishing apps.
  * Publishing is queued during high traffic
  * No silent failures or stuck states
  * Clear feedback on progress
* **Improved App ↔ Agent Communication** - Better real-time interaction between your app and agents.
* **Backward Compatibility** - Platform updates won’t break your existing apps.

## Agent Improvements

* **Memory Optimization** - Agents now run smoother with fewer crashes.
  * Fixed memory leak issues
  * Reduced memory usage
* **PII Masking (Relaunch)** - Your data is handled more safely and consistently.
  * Bug fixes and improvements to data protection
* **Agent Reliability Fixes** - Agents behave more predictably and errors are easier to understand.
  * Fixed agent import issues
  * Clearer error messages in API Call Skill
* **Model Resilience** - Agents keep working even if one model provider has issues.

  * Automatic switching between providers during outages

  **Stay Tuned: What’s coming up in Agent Builder**

  * Agent Runtime 1.2 will bring to you;
    * Faster execution
  * More consistent outputs
  * Better safety guardrails

## Platform & Integrations

* **Export Apps with Agents**
  * Your app and its agents move together, export them fully or sync both to and from GitHub seamlessly.
* **Referral Tracking**
  * Track user acquisition with UTM-based referral codes to understand where your users are coming from.

## Usage Tracking (Platform-Wide)

* **Track Your Usage (New)**\
  See exactly how your credits and tokens are used across apps, agents, and actions - with clear insights to help you optimize usage.

## Billing & Credits (Platform Enablement)

* **Better Credit Management** - Know and control how your credits are used.
  * Real-time tracking and allocation
  * Pay-as-you-go support
* **Clear Billing Visibility** - Easily understand your usage and charges.
  * Usage and billing dashboard
* **Subscriptions & Payments** - Simpler way to manage plans and payments.
  * Plan purchase and management
  * Recurring billing support
  * Automated invoices

With these updates, the platform moves closer to enabling seamless, production-grade app and agent development at scale.

There’s more coming in the days ahead — keep building and sharing your feedback with us.

**Happy Building!**


---

# 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.uptiq.ai/release-notes/2026/march-30th-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.