# Started getting Error message: "Multiple rows returned with uselist=False ..." **URL:** \ **Category:** Development: Platform\ **Created:** [April 30, 2026, 10:07am UTC](https://wazo-platform.discourse.group/t/started-getting-error-message-multiple-rows-returned-with-uselist-false/1757 "2026-04-30T10:07:04Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Ramblin](https://yyz2.discourse-cdn.com/free1/user_avatar/wazo-platform.discourse.group/ramblin/32/34_2.png) [@Ramblin](https://wazo-platform.discourse.group/u/Ramblin)\ **Post date:** [April 30, 2026, 10:07am UTC](https://wazo-platform.discourse.group/t/started-getting-error-message-multiple-rows-returned-with-uselist-false/1757/1 "2026-04-30T10:07:04Z")
I have recently started getting an error message reported in my daily logs email: Subject: Cron [root@wazopbx](mailto: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 ---
**Author:** ![chuckl](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chuckl](https://wazo-platform.discourse.group/u/chuckl)\ **Post date:** [May 14, 2026, 2:55pm UTC](https://wazo-platform.discourse.group/t/started-getting-error-message-multiple-rows-returned-with-uselist-false/1757/2 "2026-05-14T14:55:52Z")
Hi Ramblin. This is a warning, not an error. The cause is well known and no real problem should result from it. The cron job could be modified to filter out such warnings (using `| grep -v 'SAWarning'` appended to the command). ```sh $ cat /etc/cron.d/wazo-call-logd # # cron jobs for wazo-call-logs # 25 4 * * * root . /etc/profile.d/xivo_uuid.sh && /usr/bin/wazo-call-logs | grep -v 'SAWarning' ``` We may fix this in the future, but it is of low priority right now.