Unfortunately , the blocking happened again . and blocked process report capture nothing . I run the SOL SEVER report- activity -all blocking transaction during the blocking to show the blocking transaction .

blocking statement

key 59 --

key 51 update M_SYSTEM_CONFIG set sys_value = sys_value +1 where Getdate() > eff_start_dt and sys_key= 'LAST_USED_LOG_ID'

what kind of blocking is not able to trace by the profiler ? and why sql server showing -- in the blocking statement ?