> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/developer-tools/automator/automator-version-3.2.1.md).

# オートメーター 3.2.1

2024年3月18日リリース

### 概要

バージョン3.2.1には以下の向上点とバグ修正が含まれています。

* **KAA-88**: サードパーティのライブラリを更新し、発生した関連エラーを修正
* **KAA-93**: Automatorによるチーム承認の失敗を防ぐためRSA公開/秘密キー形式を修正
* **KAA-89**: SSL\_CERTIFICATE環境変数が使用されている場合に HTTPSを正しく有効にするように修正
* **KAA-85**: ヘルスチェックのレート制限を引き上げ
* **KAA-94**: Automator の再起動中にKeeper Cloudから保存された設定を正しく復元しない不具合かあ-85を修正

### アップデート手順

* コンテナのデプロイについては、コンテナをアップデートしてサービスを再起動してください。
* その他のデプロイ方法でのアップデート手順については、[こちらのページ](/sso-connect-cloud/jp/device-approvals/automator/azure-container-app.md)をご参照ください。

### 高度な設定

Automatorサービスの新しい高度な設定については[こちらのページ](/sso-connect-cloud/jp/device-approvals/automator/advanced-settings.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.keeper.io/release-notes/jp/developer-tools/automator/automator-version-3.2.1.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.