bsiggel/motia
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Remove redundant conflict resolution logging in handle_update function

Browse Source
This commit is contained in:
bitbylaw
2026-02-07 21:53:37 +00:00
parent bed3c09bb1
commit d5bc17e454
1 changed files with 0 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
bitbylaw/steps/vmh/beteiligte_sync_event_step.py
View File

@@ -314,11 +314,6 @@ async def handle_update(entity_id, betnr, espo_entity, espocrm, advoware, sync_u
extra_fields={'advowareRowId': new_rowid} extra_fields={'advowareRowId': new_rowid}
) )
context.logger.info(f"✅ Konflikt gelöst (EspoCRM won), neue rowId: {new_rowid[:20] if new_rowid else 'N/A'}...") context.logger.info(f"✅ Konflikt gelöst (EspoCRM won), neue rowId: {new_rowid[:20] if new_rowid else 'N/A'}...")
conflict_msg,
extra_fields={'advowareRowId': updated_advo.get('rowId')}
)
context.logger.info(f"✅ Konflikt gelöst: EspoCRM → Advoware")
except Exception as e: except Exception as e:
context.logger.error(f"❌ UPDATE fehlgeschlagen: {e}") context.logger.error(f"❌ UPDATE fehlgeschlagen: {e}")