Time out issue with Time Tracking app
Hello,
Some of our Support Agents have been experiencing an issue (screenshot attached) with the Time Tracking app where it times out and prevents the submission of the ticket.
This is a known issue when the ticket.save hook takes longer to resolve the Promise and global timeout period of 60 seconds is over. We reached out to Zendesk Support team (ticket# 6671191) and they were able to identify this issue with the Time Tracking app, but were not able to provide a resolution. They advised posting about it here.
If this is an expected behavior with the current version of the app, could this be resolved in a future release?
Thanks,
Korak
-
We are experiencing the exact same issue. We have narrowed the issue down to a single agent, but are unsure what to do.
-
We are also experiencing this exact same problem but with multiple agents. Can this be resolved as we need it to report on handle time for tickets.
-
Hi DJ and anyone else still getting updates here! The behavior that is being noted here is expected if the ticket submission takes longer than 60 seconds, which we note in our documentation. This would not be something that could be handled within the app, as this is a necessary component to ensure that an unresolved promise doesn't continue indefinitely, holding up the entire ticket.save lifecycle. I would recommend reviewing the settings that you have in place for the Time Tracking app to ensure that they are configured in a way that works best for your agents to ensure that this doesn't happen as frequently or at all.
-
We're noticing this issue more lately, it started about a month ago. It happens well before 60 seconds have passed making an update, is there any other viable solution for this time out issue?
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
4 Kommentare