I have script listeners setup on my Jira Cloud that automate updating fields for Jira tickets.
These listeners have been working fine for over a year.
In the last month or so, we have been getting many errors with the following pattern:
CorrelationId: XXXXXX RUN Script identifier: YYYYYYYY com.adaptavist.sr.cloud.events.WebhookExecution (jira:issue_updated webhook fired for issue AA-5407) Script name: Automated fields Took: 34100ms Logs: 2020-01-31 02:45:39.898 ERROR - Socket connection timed out on receiving data - GET /rest/agile/1.0/issue/AA-5407. The Unirest timeout defaults can be extended as described on this page: https://github.com/Mashape/unirest-java#timeouts. Please remember though that the maximum invocation time of your code is 30 seconds. 2020-01-31 02:45:39.899 INFO - GET /rest/agile/1.0/issue/AA-5407 asObject Request Duration: 30178ms 2020-01-31 02:45:39.984 ERROR - java.net.SocketTimeoutException: Read timed out 2020-01-31 02:45:40.020 ERROR - Class: com.adaptavist.sr.cloud.events.WebhookExecution, Config: null
These errors occur, every time we move tickets from one sprint to the next (i.e. on Sprint close), upon which we get around 10+ such errors. They also occur throughout the week at random intervals.
1. What is the possible cause of these errors only recently occurring? We have not changed anything in our scripts recently.
2. How do we fix this?
When working in customer support, it’s crucial to calculate, analyze and monitor specific numbers, called KPIs (Key Performance Indicators). They go hand-in-hand with customer satisfaction, problem d...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events