In a JSM project, SLAs are defined based on priority; for priority 'low', 48 hours to resolution are specified. Sporadically, the problem occurs that for tickets with low priority, the SLA displays a completely incorrect value, e.g. 1w 2d instead of 48h, and the time to resolution is also inaccurate. What could be causing this, even though the priority has not been changed?