End users can't do much from web interface and in the stdlog message like
02/17 11:22:47.03 sdm-server-name domsrvr 13372 ERROR attr.c 6201 No response to trigger cr::attached_sla_processing (4 time) after 240 seconds; waiting another 480 seconds
This tech doc documents one reason why this happens.
Release : 17.3
Make sure you don't have some external mdb database load during the work hours---if you do, some Service Desk data will be locked which causes the SDM triggers to fail and then clog the app.
SDM admins should check the work load/performance, recent customization, recent product upgrade as well. DB load is only one reason this could happen.