Reruns

Last updated 2 days ago

Was this helpful?

Reruns

As a Pandium user, there may be instances where I need to rerun a sync for one of my tenants. It's possible that my initial run didn't capture all the necessary data that I was hoping to see synced over. This could be because details or values in the target systems may not have been properly set, or maybe my team has simply updated our tenant configuration settings or switched to a new release version. Whatever the case may be, you have the ability to trigger a rerun for a previously synced job.

To trigger a Rerun, perform the following steps:

Pull up the tenant in question
1. You can do this by pulling up the integration or by going to Manage > Tenants
Navigate to the run details page for the job you wish to rerun
1. You can also locate the desired run by navigating to Manage > Runs and filter out your search results using the enhanced sorting and filtering resources.
Once you have pulled up the run details page, look for the RERUN option in the top right of your screen and select it.
You should now be presented with a popup window that says "Are you sure you want to rerun this run?". You should see three options listed below:
1. Rerun with original configuration - When selecting this option, you will be using the integration release, STDOUT, and configs that the original received.
2. Rerun with current configuration of tenant - When selecting this option, you will be using the integration release, STDOUT, and configs that are currently set on the tenant.
3. Rerun with custom configuration - When selecting this option, you will be presented with the opportunity to customize the integration release, STDOUT, and configs for this rerun, with default values populated from the original run.
Select one of the options above and press NEXT.
1. If you selected Rerun with original configuration or Rerun with current configuration of tenant, you should be presented with a new option that says "Do you want to save the STDOUT and context from this rerun to be used in future runs?" By default, No will be selected.
2. If you select Rerun with custom configuration, then you will be taken to a new screen that will allow you to modify the Release, STDOUT, and Configuration details. Once you have modified your details and selected RERUN, then you will be asked if you wish to save the STDOUT and context from this rerun to be used in future runs.
  1. Release - Do you want to use a different release version?
  2. STDOUT - Modify what will be passed into the environment variables PAN_CTX_LAST_SUCCESSFUL_RUN_STD_OUT and PAN_CTX_LAST_RUN_STD_OUT.
  3. Configuration - Are there any tenant settings that you missed last time?
Once you have selected one of the following rerun options, you will be brought back to the tenant details page and there should be a new run created with a trigger that says rerun.
1. Please Note: If you pull up the details for this new run, you will notice the rerun option is greyed out even after the sync finishes. We currently do not support the ability to rerun a rerun. If you wish to trigger another rerun for the original run ID, then you will need to start from steps 1 and 2 respectively.

Last updated 2 days ago

Was this helpful?

To trigger a Rerun, perform the following steps:

Pull up the tenant in question
1. You can do this by pulling up the integration or by going to Manage > Tenants
Navigate to the run details page for the job you wish to rerun
1. You can also locate the desired run by navigating to Manage > Runs and filter out your search results using the enhanced sorting and filtering resources.
Once you have pulled up the run details page, look for the RERUN option in the top right of your screen and select it.
You should now be presented with a popup window that says "Are you sure you want to rerun this run?". You should see three options listed below:
1. Rerun with original configuration - When selecting this option, you will be using the integration release, STDOUT, and configs that the original received.
2. Rerun with current configuration of tenant - When selecting this option, you will be using the integration release, STDOUT, and configs that are currently set on the tenant.
3. Rerun with custom configuration - When selecting this option, you will be presented with the opportunity to customize the integration release, STDOUT, and configs for this rerun, with default values populated from the original run.
Select one of the options above and press NEXT.
1. If you selected Rerun with original configuration or Rerun with current configuration of tenant, you should be presented with a new option that says "Do you want to save the STDOUT and context from this rerun to be used in future runs?" By default, No will be selected.
2. If you select Rerun with custom configuration, then you will be taken to a new screen that will allow you to modify the Release, STDOUT, and Configuration details. Once you have modified your details and selected RERUN, then you will be asked if you wish to save the STDOUT and context from this rerun to be used in future runs.
  1. Release - Do you want to use a different release version?
  2. STDOUT - Modify what will be passed into the environment variables PAN_CTX_LAST_SUCCESSFUL_RUN_STD_OUT and PAN_CTX_LAST_RUN_STD_OUT.
  3. Configuration - Are there any tenant settings that you missed last time?
Once you have selected one of the following rerun options, you will be brought back to the tenant details page and there should be a new run created with a trigger that says rerun.
1. Please Note: If you pull up the details for this new run, you will notice the rerun option is greyed out even after the sync finishes. We currently do not support the ability to rerun a rerun. If you wish to trigger another rerun for the original run ID, then you will need to start from steps 1 and 2 respectively.