> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/pipeline-forms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/pipeline-forms/user-guides/user-guide/audit-logs.md). # Audit logs There are two type of logs available in PFO: * Execution logs * Audit logs ## Execution logs In the execution logs, all pipelines are listed which were executed through PFO:

Column	Values
Icon	Pipelines can be executed - manually (person icon) - scheduled (pipes icon)
Action	Scheduled name (if there is any) - The name of the form, that was used for execution
Result	SUCCESS when the pipeline is triggered, FAILED in any other cases (eg.: when you've reached the execution limit for your plan)
Date	The date of the execution in your timezone

Click on any row in the logs to showcase all details for that execution entry:

## Audit logs In the Audit logs, every user interaction related to the configuration is listed:

Column	Values
Action	One of the following actions: - Create schedule - Update schedule - Toggle schedule - Delete schedule
Result	SUCCESS when the pipeline is triggered, FAILED in any other cases (eg.: when you've reached the execution limit for your plan)
Date	The date of the execution in your timezone

Click on any row in the logs to showcase all details for that execution entry:

--- # 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.meta-inf.hu/pipeline-forms/user-guides/user-guide/audit-logs.md?ask=&goal= ``` `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.