> 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/2023-dev-updates/february-17th-2023.md).

# February 17, 2023 - 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!

<details>

<summary><strong>New features and items</strong></summary>

* Throw error when an unreasonable value is entered for password length
* Allowed for POST to a workbook using the Graph API

</details>

<details>

<summary><strong>Bug fixes and chores</strong></summary>

* Fixed password field in graph actions not passing actual value
* Bugfix: Can't update the name of any org var
* Bugfix: Missing transition arrows for shallow clones
* Bugfix: Problem creating org (via csp). (Or, at least we're now surfacing a descriptive error msg)
* Bugfix: Webhook secrets weren't working for sub-org trigger instances
* Upgraded and added additional postgres read-replicas to handle large clone-sync jobs

</details>

<details>

<summary><strong>In review, testing and development</strong></summary>

* Add timezone support for cron triggers
* Fix cloning items with circular references
* Microsoft graph subscription triggers
* SonicWall

</details>

If you'd like to see these in action, review the latest [Open Mic recording here](/updates/roc-open-mics/roc-open-mics-north-america/2023-roc-open-mics/february-17th-2023-trigger-review-and-qa.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 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/2023-dev-updates/february-17th-2023.md?ask=<question>&goal=<user_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.