Adobe Campaign – New offer spaces stop returning propositions after an offer was deleted (not deactivated). Architectural impact? Alternatives to rollback?

Context / Environment

• Product: Adobe Campaign (Hosted)
• Area: Offers / Offer Spaces / Propositions used within complex workflows
• Implementation: Custom logic around offers and offer spaces, used as a central decision point inside multi‑segmentation workflows

What happened

• An offer  was deleted instead of being deactivated.
• Since that deletion:
  • New offer spaces and new offers mapped to these spaces no longer return propositions in workflows.
  • The enrichment step remains empty when using these new configurations.
• Existing/older configurations seem unaffected (symptom primarily on new objects & mappings).

Why this matters

• Our workflows are fairly advanced:
  • Multiple segmentations on the target population
  • Eligibility rules + business logic
  • An offer space is used as a central decision point (takes segmentation outputs → applies rules/eligibility → returns propositions → injected into delivery)
• Support/Engineering believes the deletion likely broke internal relationships within our customized offer implementation (offers, offer spaces, propositions, and the custom schema/logic that ties them together).
• Restoring to a snapshot before the incident would recover offers, but would rollback everything else (workflows, tracking, delivery logs, other data changes) since that date—too risky for us.

Constraints

• No partial DB restore option on Hosted.
• Full rollback is business‑prohibitive due to data loss and operational impact.
• We must restore the ability to create/use new offer spaces & offers without destabilizing running operations.

What I’m specifically asking the community

1. Root Cause Patterns:
   Have you seen new offers/spaces fail to produce propositions after an offer deletion?
   • What specific relationships or custom extensions tended to break (foreign keys, internal references, JS lookups, schema link types, typology or eligibility bindings, access rights/inheritance)?
2. Safe Remediation Without Rollback:
   What step-by-step approach worked for you to repair the graph of offers/offer spaces/propositions?
   • Did you re‑create certain objects (e.g., the offer space) and relink flows?
   • Any scripts or utilities you used to rewire relationships safely?
3. Decision Engine Refresh:
   Are there known caches or publication layers that must be reset/republished after structural changes in offer objects to make new propositions appear?
4. Do’s & Don’ts Post‑Incident:
   Any pitfalls to avoid (e.g., touching legacy objects that still work, editing schemas directly in prod, mass updates on nms:* tables)?
   Any must-do checks before bringing in PS (so we don’t waste discovery time)?

Extra details if helpful

• The Enrichment step is empty specifically when using new offer spaces/offers; older ones still behave as expected.
• Multiple segmentations feed into a single central decision point (offer space), which returns propositions.
• We suspect that deleting (rather than deactivating) an offer invalidated internal references in our custom wiring.

Goal

• Regain the ability to create and use new offer spaces/offers and get propositions returned in workflows—without a full environment rollback—while minimizing disruption to current operations.

Any war stories, checklists, or tactical remediation steps would be greatly appreciated.

Thanks in advance!