> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/editable/admin-portal-and-editable-console/utility/pipeline/logs-and-other-pipeline-options.md). # Logs & other pipeline options This section explains the configuration options and the logs screen available in the pipeline configuration window. ## 1. Sync report Clicking the 'sync' icon refreshes and syncs the report, ensuring the newly added visuals are included, if any.

Sync report

## 2. Edit report You can edit a report pipeline by clicking on the pencil icon, as shown below.

Edit report pipeline

### 2.1. Edit destination mapping To change the stage destinations, use the dropdowns and select the required data source and table for each stage. Click **Update.**

Edit destination

### 2.2. Add/remove visuals from deployment When deploying a report, you can choose to include or exclude any visuals by enabling or disabling the '**Add To Pipeline**' toggle button. Then, click **Update.**

Add to or remove from pipeline

## **3. Delete report from pipeline** Use the bin icon to delete the report from the pipeline.

Delete report from pipeline

## 4. Logs Switch to the **Logs** tab to view the list of pipelines deployed by all workspace users.

Logs

You can use the search box to find specific logs by ID. You can also filter the logs based on the 'from' or 'to' stages, deployment status, and the person who deployed the pipeline.

Search and filter deployment logs

Click **Reset All** to reset all applied filters. --- # 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.inforiver.com/editable/admin-portal-and-editable-console/utility/pipeline/logs-and-other-pipeline-options.md?ask=&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.