Skip to main content
This typically happens after cloning a bundled campaign — the clone is missing the connections between the bundle and its child campaigns.

​
Symptoms

  • A Real-Time webhook response shows an Invalid ID
  • The Invalid ID matches the campaign ID set up in the network
  • The campaign was previously cloned from a bundled campaign
Applies to: Real-Time Routing

​
Cause

Cloning a bundled campaign is the root cause — the clone doesn’t automatically carry over the connections between the bundle campaign and each of its child campaigns.

​
Resolution

Edit the round-robin IVR node to include all campaigns designated as bundled destinations. This creates the missing connections between the bundle campaign and each child campaign, so the bundle functions correctly — you can discard the revision afterward, since the original campaign should now work as expected. Alternatively, create a new bundled campaign from scratch instead of cloning an existing one.

​
Where to go next

Last modified on September 25, 2026