Why is a form submission linked to the wrong renewal record?
This is a known behavior in SDL Connect, not a bug in linking.
Root cause: Renewal submissions are linked to the specific submission they were sent from. The renewal association is tied to the original submission record at the time the renewal notification was sent.
Result: If a renewal needs to be moved from one record to another (e.g., it was sent from the wrong submission), that can't be done from the UI — it requires an escalation to SDL support.
How to resolve: Contact SDL support to reassign the renewal association to the correct record.
Related behavior to check first:
- Confirm the renewal notification was triggered from the correct submission. If the wrong submission triggered the renewal email, the link will follow that submission.
- Advanced Workflow renewal triggers control which submissions generate renewal notifications — verify the trigger is configured to fire on the intended records.
If you're seeing a different symptom — like a renewal form pre-populating with data from an unexpected prior submission — that's also expected: date fields on renewal forms pre-populate from the previous submission by design, and this can't be suppressed with a "none" default expression on the field.