> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/development-updates/2025-dev-updates/march-21st-2025.md).
# March 21, 2025 - Dev update
Explore what new changes the Dev team has deployed in the last week!
This can be anything from new features, bug fixes, or QoL changes!
New features and items
* Improved error messaging of Jinja trigger criteria
* Added persistent sorting of App Builder data tables
Bug fixes and chores
* Created table and relations prerequisite work for syncing custom App Builder components
* Moved crate publishing processing from agents that affect workflow processing
* Fixed configurations in error tracking tool for improved bug triaging and diagnosis
* Added check for E\_OK status in SonicWall NSM generic action to prevent false positive failures
* Fixed broken SuperOps action options
Coming Soon
* Generic GraphQL Request Action to the Rewst Integration
* Improved workflow page and workflow results page search and filter
* Workflow executions dashboard widget
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.rewst.help/updates/development-updates/2025-dev-updates/march-21st-2025.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.