I have recently started getting an error message reported in my daily logs email:
Subject: Cron root@wazopbx . /etc/profile.d/xivo_uuid.sh && /usr/bin/wazo-call-logs
Body:
2026-04-30 04:25:09,850 [2249390] (ERROR) (STDERR): /usr/lib/python3/dist-packages/wazo_call_logd/database/queries/call_log.py:308: SAWarning: Multiple rows returned with uselist=False for lazily-loaded attribute ‘CallLog.destination_participant’
2026-04-30 04:25:09,850 [2249390] (ERROR) (STDERR): call_log.destination_participant
The proposed (by AI) issue/solution is (but I do not know where to find the SQL code to fix)
Occurs when a one-to-one relationship (uselist=False) expectedly maps one row, but the database returns multiple rows for CallLog.destination_participant, often caused by mismatched join conditions or duplicate call logs. You can fix this by enforcing a LIMIT 1 via order_by in the relationship or fixing data inconsistency.
Is anyone else seeing this and if so, how did you resolve?
I am on Wazo 26.03