tpp-workflow-stale-entity-mapping
TPP / Workflow Stale Entity Mapping (Conditional Logic)
What This Skill Debugs
Symptom: For a TPP (third-party paper / upload) workflow, conditional logic that depends on creator-party entities (or similar) shows fewer selectable entities in the UI than the Contract Type / workspace settings show — e.g. only one entity in the dropdown when two are configured.
Nature: This is usually data consistency, not a live 5xx or flaky dependency. Logs/traces often show nothing useful unless a failed admin/API call was captured.
Historical context (engineering, incident thread): Through 2025-09-14, when a new organization entity was created after an existing workflow was already created, that entity was not automatically linked to that workflow’s entity mapping set. A prod fix landed 2025-09-15 so new entities are synced to relevant workflows going forward. Older workflows can still have stale mappings until clone or backend remap/resync.
Know example (for calibration only — use placeholders in new incidents): Rootly incident “Missing entity in TPP workflow conditional logic”, Jira SPD-42665, related class SPD-35479 (child contract type / draft workflow entity visibility).