Jump to content

Search the Community

Showing results for tags 'resume'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Hornbill Platform and Applications
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Service Manager
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Configuration Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Organisation


Location


Interests


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 2 results

  1. Hi I'm see in the following error when resuming a call from paused, any ideas? 240556 2018-02-27 09:11:21 error perf 10852 apps:takeRequestOffHold() Method call results: failure (202137600 B, 461 ms, -2160 kB, 1 ms, 0 kB) 240555 2018-02-27 09:11:21 error scripts 10852 nodeName: Invoke Flowcode: Take response timer off hold; nodeId: 4b8db1a8-c819-4e8f-a86d-b91da1bc609d; At 307/1: "Uncaught EspMethodCall:invoke: Operation[apps/com.hornbill.servicemanager/Requests:takeResponseTimerOffHold] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold): Schema validation: Mandatory (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold/adjustedTime)" throw(e); _fc_node_exec_4b8db1a8_c819_4e8f_a86d_b91da1bc609d 240554 2018-02-27 09:11:21 error comms 10852 Operation[apps/com.hornbill.servicemanager/Requests:takeResponseTimerOffHold] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold): Schema validation: Mandatory (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold/adjustedTime) 240553 2018-02-27 09:11:21 error perf 9596 apps:takeResponseTimerOffHold() Method call results: failure (204374016 B, 112 ms, -64 kB, 0 ms, 0 kB) 240552 2018-02-27 09:11:21 error scripts 9596 nodeName: API Call: Query Timer; nodeId: 3d6f2ad2-d3f1-4646-8843-09e1e53cd6b6; "EspMethodCall:invoke: Operation[time:timerQuery] The specified timer [34215] was not found" 240550 2018-02-27 09:11:21 error comms 9596 Operation[time:timerQuery] The specified timer [34215] was not found 240548 2018-02-27 09:11:21 error perf 11044 time:timerQuery() Method call results: failure (206479360 B, 3 ms, -8 kB, 0 ms, 0 kB) 239427 2018-02-27 09:10:38 error perf 15428 apps:takeRequestOffHold() Method call results: failure (199073792 B, 379 ms, -40 kB, 0 ms, 0 kB) 239426 2018-02-27 09:10:38 error scripts 15428 nodeName: Invoke Flowcode: Take response timer off hold; nodeId: 4b8db1a8-c819-4e8f-a86d-b91da1bc609d; At 307/1: "Uncaught EspMethodCall:invoke: Operation[apps/com.hornbill.servicemanager/Requests:takeResponseTimerOffHold] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold): Schema validation: Mandatory (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold/adjustedTime)" throw(e); _fc_node_exec_4b8db1a8_c819_4e8f_a86d_b91da1bc609d 239425 2018-02-27 09:10:38 error comms 15428 Operation[apps/com.hornbill.servicemanager/Requests:takeResponseTimerOffHold] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold): Schema validation: Mandatory (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold/adjustedTime)
  2. Is it possible to restart/resume an SLA timer without resetting it? We have a situation where we stop the SLA timer as our 1st Tier has identified the customer has said the issue is resolved, but sometimes this is not correct, so we would want to put a secondary check in the workflow and if it is not correct route the workflow back to the investigation steps and restart/resume the timer. I know I could get around it by using a sub status under hold and not changing to resolved until double checked but wanted to know if it was possible to reverse the stopping the timer. Cheers Martyn
×
×
  • Create New...