Run Normal Sync on the Tenant

Your normal sync prints a standard out that specifies the ID for that run's Pokémon of the Day. Let's run a normal sync for the tenant to see how that gets passed through context to the next run.

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.

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.

1. Click the arrow on Sync Now > Normal Sync. This will kick off a normal sync for your tenant, which will appear in the Activity 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.

1. Click the icon in the run's Status column. This will display the Activity 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"}

1. Navigate back to the Tenant Detail page by clicking the tenant's name at the top of the Activity Detail page.

To confirm that context is correctly being passed from one run to the next, start another normal sync.

1. 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.

2. Locate the run in the Activity list at the bottom of the Tenant Detail page, and click on the icon in the run's Status column. This will display the Activity Detail page for the run.

The log in the Activity 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!