Introducing Reruns – A Better Way to Manage Integration Syncs in Pandium

Even the best integrations fail sometimes, whether it's a provider outage, a config change, or a release bug that’s to blame. 

That’s why we built our new Reruns feature within our admin dashboard. It’s our latest addition to Pandium’s that’s making integration lifecycle management smoother.

Now, teams using Pandium can re-execute integration jobs directly from within Pandium’s Admin Dashboard. This means even customer support functions can go in and rerun syncs and resolve issues. 

How to Use the Reruns Feature 

Just head to the left-hand navigation in the Admin Dashboard, click “Runs,” select the run you’d like to rerun, and choose from three flexible options:

1. Rerun with the Original Configuration

What this means:
Replays the run exactly as it happened the first time. Uses the same integration release, configuration, and standard out (STDOUT) that were originally used.

When would this be useful?
Perfect for when something went wrong outside your control—like an API being temporarily down, a brief network hiccup, or a platform-specific outage. Your logic is still solid, the timing just wasn’t right.

2. Rerun with the Current Configuration of the Tenant

What this means:
Replays the run using the tenant’s current configuration and release. This reflects any updates made since the original run.

When would this be useful?
Great if you’ve recently fixed a bug, rolled out a new release, or changed configuration settings, and want to retry a failed run using that updated logic or structure.

3. Rerun with a Custom Configuration

What this means:
Gives you full control over the rerun, meaning you can mix and match any combination of release, configuration, context, or STDOUT. Default values are pulled from the original run, but you can modify them as needed.

When this can be useful:
Perfect for complex or one-off situations where you need to tweak something specific:

• Change the release version while keeping most of the original settings
  
  
• Update the STDOUT to remove conflicting data
  
  
• Test a fix without changing tenant-wide settings
  
  

This is especially useful for debugging or recovering from unusual data conditions.

Why It Matters

Faster issue resolution
Support and CX teams can fix failed syncs themselves, without escalating to engineering or waiting on code updates.

More flexible recovery workflows
Rerun individual jobs without triggering full flows or disrupting downstream processes. Great for quietly recovering from failure and maintaining a clean user experience.

Built for developer velocity
Test with different configs or releases, run snapshot jobs, and validate fixes instantly, all from Pandium’s UI.

Scalable lifecycle management

Say goodbye to back-and-forth with support. Say hello to a more self-serve, developer-friendly way to manage and scale your integration operations.

Pandium’s rerun feature strengthens your control over the integration lifecycle and makes it easier to keep syncs reliable, even under pressure.