Root Cause: - Previous index-based mapping assumed signals come in same order as questions - But LLM response order can differ from question configuration order - Led to signal values being assigned to wrong question IDs Old Logic (BUGGY): 1. Build question_type → [list of IDs] 2. Track index per type 3. Get Nth ID from list → Assumes LLM answers in question definition order ❌ New Logic (CORRECT): 1. Build question_type → question_id (direct mapping) 2. For each signal: lookup type → get ID → Order-independent ✅ Backend workflow_executor.py: - Removed index tracking (type_counts) - Direct lookup: question_type_to_id[signal.question_type] - Added ERROR log if duplicate question types found - Added INFO log for each mapped signal (debugging) Important: - Each question MUST have a UNIQUE type - If two questions share same type: ERROR logged - System designed for unique types (LLM can't answer duplicates) Example Debug Output: ``` Mapped signal: protein_ausreichend → signal_q21 = 'nein' Mapped signal: kohlenhydrate_strategie → signal_q1775... = 'von Proteinen' ``` Issue: Signal values assigned to wrong question IDs Version: 0.9p (workflow module) Part 3: End Node Template Engine - Signal Mapping Fix Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>