> For the complete documentation index, see [llms.txt](https://docs-embed.anyflow.jp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-embed.anyflow.jp/ops/solution-history.md).

# 実行履歴

ソリューションの実行履歴はエンドユーザー向けとベンダー向けで内容が異なります。

### [エンドユーザー向け](/ops/solution-history/for-endusers.md)

* ウィザードでの確認
* 実行日時、ステータス、ログメッセージが確認可能
* ログメッセージは、ソリューションのエラーログおよびログアクションの結果のみ

### [ベンダー向け](/ops/solution-history/for-venders.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 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-embed.anyflow.jp/ops/solution-history.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.