SC Task closed complete but closed and closed by fields not updated

[Kevin Paul]

Hi All,

We have a thousand records in sc_task table where state is Closed Complete, Closed Skipped or Closed Incomplete but the fields like, closed and closed by are empty. In the xml of the records, the updated by date is different to the date in the audit history table. If I think that these records have been closed using background scripts then I could find in the history table only one occurrence of the state field where it is already closed.

Please help me investigate this further. We have thousand similar records like this and root cause for this is needed.

Thanks in advance,

Kevin

[SatyakiBose]

Hello @Kevin Paul 

Well digging into this might be a little challenging.

Do we know approximately when the values were changed?

If not, what could have happened is:

• records were imported from another instance.
• the date and time format on the source instance was different from the target instance.
• the updated by field had values which were not present in the target instance, therefore system left is empty.

In such cases, the log files really come in handy.

But for that we also need to know the timeframe when these values were changed.

You can check in the background script execution history if any script was run to change the values of these records.

[bvlo]

Kevin,

Did you ever find a solution to this issue? We are facing the same issue and it appears that when our flow(s) run, they run as "system". When this occurs closed_by displays empty. Support is telling us this is expected behavior. I am curious if you found this to be the case. For us, having closed_by empty is less than ideal. 

[Ian Mildon]

This would be something "server-side" as anything user generated would be recorded in the sys_updated_on, sys_updated_by and/or other similar fields and show in the XML.

[Vasu ch]

Hi @Kevin Paul 

Have you come across any solution for this? We got the same issue. 

Regards,

Vasu Ch