7oaks Posted August 29, 2023 Share Posted August 29, 2023 Good Morning - hope someone can assist with this for me. A colleague started a call that was logged on the 21st August and resolved on the same day. The resolution date was a week later but the Service level is showing as being missed. Any suggestions on how it happened and is there a way to amend it. I have attached a screenshot. Link to comment Share on other sites More sharing options...
Steve Giller Posted August 29, 2023 Share Posted August 29, 2023 If you don't have a Mark Response Timer and the app.request.stopResolutionTimerOnResolve is not set to on it may be simply that your Workflow is starting the Timer and never stopping it. Link to comment Share on other sites More sharing options...
7oaks Posted August 29, 2023 Author Share Posted August 29, 2023 I'll check that thanks Steve - not had it before though so will see what result i get. Link to comment Share on other sites More sharing options...
7oaks Posted August 30, 2023 Author Share Posted August 30, 2023 Steve, yes strangely this was disabled so now enabled again and i will check some calls to make sure its stopping the timer. Thanks for the advice. Debby Link to comment Share on other sites More sharing options...
Steve Giller Posted August 30, 2023 Share Posted August 30, 2023 Just to clarify, there is no requirement to have this setting enabled, you can control the Timers solely using the BPM nodes, so it may be that having it disabled in your Instance is the desired setting. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now