Is it possible that records on the broadlog table that are in a pending status b/c you wish to confirm the delivery before sending can have their broadlog ids change once they are approved and the status is changed to sent? I am seeing some instances where broadlog ids for records that are pending are getting changed to new broadlog ids if the user updates the wave definition in the delivery properties and hits 'Save' and then clicks the 'Confirm Delivery' button to enable the records to be delivered.
This is totaly classic. The broadlogs doesn't have their id changed, but simply new broadlog are created as the target is recalculated.
When you prepare several times the same delivery, the previously calculated broadlogs are deleted and new broadlogs are created.
You can see it with the message 'Cleaning of previous analysis datas' or something similar into the delivery audit.
Aslo, you could see similar as broadlog datas when the target is just estimated, but this is not "broadlog", this is just temporary datas named "temp:forecastLog". Those datas are not visible in a classical way with the console, only when opening a delivery (no real schema are mapped as each delivery build his own table).