> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/write-the-integration-in-typescript/run-normal-sync-on-the-tenant.md).
# Run Normal Sync on the Tenant
Before you can try out your new normal sync you will need to put your tenant on a new release based on your new code. To do that follow all the steps in the [Check the Customized Connection Settings Page](/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/write-the-integration-in-typescript/check-the-customized-connection-settings-page.md).
1. Once your tenant is on that new release, navigate to your integration's tenant by clicking **Integrations** from the side bar > the **Unpublished** tab > the card for your *Pokémon of the Day* integration > the **Tenants** tab > the row for your tenant.
2. Click the arrow on **Sync Now** > **Normal Sync.** This will kick off a normal sync for your tenant, which will appear in the ***Runs*** list at the bottom of the page. Before the run is complete you should get a Slack message about the Pokémon of the Day.
3. Click the icon in the run's *Status* column. This will display the *Run Detail* page for the run.
The log there should look just like the logs for the normal syncs you ran locally during development (with the exception that the context logged out has far more information now).
The last line of the log should be the standard out and it should look something like this:
```
[OUT] {"last_pokemon_id":"1"}
```
4. Navigate back to the *Tenant Detail* page by clicking the tenant's name at the top of the *Run Detail* page.
To confirm that context is correctly being passed from one run to the next, start another normal sync.
5. Click the arrow on **Sync Now** > **Normal Sync.** Before the run is complete you should get a Slack message about a different Pokémon of the day.
6. Locate the run in the *Run* list at the bottom of the *Tenant Detail* page, and click on the icon in the run's *Status* column. This will display the *Run Detail* page for the run.
The log in the Run Detail page should be very similar to the last run but take note of a few things:
* Within the context logged at the start of the run you should be able to find `last_successful_run_std_out: '{"last_pokemon_id":1}'`. Notice that this matches the standard out the tenant's last normal sync.
* The last line of the log should be the standard out , and its ID should be greater than the last one `[OUT] {"last_pokemon_id":2}`.
Now that you've seen your code runs correctly on a Pandium tenant you just need to change the tenant's schedule so it runs on a daily basis!
---
# 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.pandium.com/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/write-the-integration-in-typescript/run-normal-sync-on-the-tenant.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.