> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/product/accounts/sync/stored-records.md). # Stored records Review, troubleshoot, or delete your data Once an app is authenticated and a sync is running successfully, Middle will begin ingesting and storing records. These records can be reviewed by clicking **Records** next to any of your app connection's record types. ## Search You are free to search any of the fields in the search panel or click on a record to view the record's associated activities at a business, any past iterations of these records, and a history of workflows that were run on the record. ![Search your data by any of the fields provided](https://932524191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mks_UuU2atghAuA9bQz%2Fuploads%2FOOZCWx0RMHzkrWXblWQ3%2FScreen%20Shot%202021-12-03%20at%204.33.55%20PM.png?alt=media\&token=7efbbf68-6d6d-40d2-93a8-214cec802313) ## Record timeline Open a record's **Timeline** to review record changes, activity trigger results, and workflow runs. Use **Record Updates** or **Workflows Executed** to filter the entries. Record changes show where the update came from and the prior record version when available. Activity trigger entries link to the **Source activity ID** and identify the **Triggering record**. A trigger can select other records as workflow inputs, so a workflow entry may refer to a change on a different record. Follow the source activity link to inspect that change. A single workflow run shows its execution report in the entry. When a trigger produces multiple runs, **Workflows executed** lists each run's input records, execution report, status, and last step. The trigger's **Executed** status means the activity was processed; check the individual workflow reports for their outcomes. Use the refresh button or enable **Autorefresh** to see new entries and updated workflow results. To evaluate a source activity again, use **Replay trigger** beside its trigger status. See [Replaying triggers](/middle-docs/product/accounts/workflow-triggers.md#replaying-triggers) for the steps, permissions, and how replay differs from re-executing a workflow. ## Execute Manual workflow executions can be run via record pages. These executions can be executed en masse by selecting workflows from a list or by selecting an entire data set. If you are reviewing a specific record, you are also able to execute a workflow to run manually on that record via the Execute Workflow dropdown menu. ![Select which records you'd like to manually run a workflow on](https://932524191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mks_UuU2atghAuA9bQz%2Fuploads%2FhUKp4yPT9GpZJ4LzQUWa%2FScreen%20Shot%202021-12-03%20at%204.35.58%20PM.png?alt=media\&token=bf2cbc68-8d88-426b-90a8-c502e4f4317c) ## Delete a record Middle allows you to manually delete individual records or set up [automated data deletion](/middle-docs/product/data-deletion.md) of stale records. To delete an individual record, check off the record or records you'd like to delete and select Delete. This wipes the record from your Middle instance. {% hint style="warning" %} Please note that this data can be synced and stored again in Middle if it has not been deleted in the source app {% endhint %} ## Export records You can initiate an asynchronous export of your stored data by clicking **Export data** at the top of the record page. You have the option to choose which fields you'd like in the export, whether only data with an updated timestamp after a specified date should be in the file, and the file format you'd like the export to be in (either `.zip` or `.bz2`). You will be emailed your desired report and you can track the status of this export in the task tracker. --- # 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.middle.app/middle-docs/product/accounts/sync/stored-records.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.