Rundetails table are spamming by scheduled task

Hello, anyone experienced an issue with rundetails being spammed and accumulated over time? Our app rely on Jira scheduling to functioning. Every time there is an issue event we create a scheduled task to handle. And after the task finished processing we see a new few entries added to rundetails as in the screenshot below. Anyone knows how to stop this behavior (spamming that table), and what is A and S mean in run_outcome table, and what Wrong thread mean in info_message column?