question Resolved time on incident is populating with future times it should not be. in Community Central forum

Resolved time on incident is populating with future times it should not be.

Kamatham Suman1 — Tue, 28 May 2024 08:21:28 GMT

Resolved time on incident is populating with future times it should not be. Resolved time should be current date and time now.
Out-of-box Business Rule "mark_resolved" is setting the resolved time of the incident.
This Issue is happening intermittently.
Is any one else Facing this issue??

Can someone help me to solve this issue or on how can i trace it.

Re: Resolved time on incident is populating with future times it should not be.

Mark Manders — Tue, 28 May 2024 08:23:13 GMT

You need to check on other flows/rules that are setting this date. When does it happen? To which users? Are there differences in time zone settings on the users?

Re: Resolved time on incident is populating with future times it should not be.

Kamatham Suman1 — Tue, 28 May 2024 10:25:08 GMT

I have checked for flows, there isn't any.
This happened a month ago for few incidents.

I don't think it could be timezone issues, because the time difference is 8 days, 13 days as such.