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

# March 23, 2026

### Workflows Improvements

We've done a big push to improve the reliability and performance of both scheduled and triggered workflows. We're actively monitoring to make sure everything continues to perform well. Here's what's new:\
\
**Scheduled Workflows**\
Scheduled workflows now run smoother and more consistently, with improvements on our end to ensure they fire on time without any delays.\
\
**Triggered Workflows**\
Triggered workflows are now better at detecting and surfacing the right data - including picking up new records, capturing changes between runs, and firing reliably across more scenarios.\
\
Additionally, we have also revamped the 'Workflows' list page to show:

* Triggered vs. Scheduled Workflows
* Next Scheduled At
* Last Run Status

<figure><img src="/files/CE1xruyz6Da7zi3G2GlL" alt=""><figcaption></figcaption></figure>


---

# 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.hockeystack.com/release-notes/q1-2026/march-23-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.