> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/patchworks-services/working-with-services/the-anatomy-of-a-service/service-summary.md).
# Service summary
## Introduction
The **summary** tab shows high-level information about how the service is performing. The tab is split into two panes - [daily transactions](#daily-transactions) (see 1 below), followed by a [sync list](#sync-list) (see 2 below).
## Daily transactions
The **daily transactions** pane displays a chart showing transactions for the defined time period. Hover your cursor over any point on the chart for details - for example:
{% hint style="info" %}
**What is a transaction?**
A transaction occurs whenever Patchworks pulls an entity (e.g. an order, refund, product or stock level) from a source system and subsequently pushes it to a destination system.
{% endhint %}
To set a time period for data shown on this chart, click the date picker:
\
Then click your starting date and move your cursor right/left to select the ending date - for example:
## Sync list
The **sync list** shows summary information for every sync (i.e. service run) that has started in the last 24 hours - for example:
You can use the search field (see 1 above) to find a particular sync entry by its **sync id**. You can also see the current status (see 2 above) and click the ellipsis (see 3 above) to access more detailed [logs](/product-documentation/patchworks-services/reporting-and-logging/service-sync-logs.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://doc.wearepatchworks.com/product-documentation/patchworks-services/working-with-services/the-anatomy-of-a-service/service-summary.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.