---
schema_version: "1"
id: d6dedf8965ecb0d0f596971c39b37dbea03ce6a0d96adf4eb45847f8ea8f873d
title: Understanding Remote Includes
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/b2c-commerce/guides/ops-troubleshooting/b2c-understanding-remote-includes.md
canonical_url: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/b2c-understanding-remote-includes.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 29a5a395c3ade9404c92f1e65cb00f5719d5203ae5b06906aa96a1600fac4cb6
products:
  - Composable Storefront
  - Salesforce APIs
---
# Understanding Remote Includes

Understanding how remote includes work can help trace problems.

Each remote include is an additional request to the Application Server, and can be cached. The Web Adapter actually assembles the page. Remote includes can include other remote includes.

## Request ID

The Web Adapter assigns a request ID to the client request. For remote includes, the request ID has been extended to uniquely identify requests that go to the Application Server with this format:

```
requestID-includeDepth-includeNumber
```

## Example

```
main request: ZAm5zUVvcQ4KAgAK-0-00
1st remote include on main page: ZAm5zUVvcQ4KAgAK-1-01
2nd remote include on main page: ZAm5zUVvcQ4KAgAK-1-02
3rd remote include on main page: ZAm5zUVvcQ4KAgAK-1-03
Remote include on 3rd remote include on main page: ZAm5zUVvcQ4KAgAK-2-04
```