> 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/march-3rd-2023.md).

# March 3, 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>

* Add IdentityRiskEvent.Read.All to permission scope

</details>

<details>

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

* Fix cloning items with circular references

</details>

<details>

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

* Add timezone support for cron triggers
* Microsoft graph subscription triggers (QA)
* SonicWall NSM
* New Crowdstrike actions for Users and Detections (QA)
* Prevent double click on new workflow submit button resulting in multiple new workflows (QA)

</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/march-3rd-2023-new-webhooks-tracking-steam-deals-and-templates-oh-my.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/march-3rd-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.