Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Lots of "socket connection timed out on receiving data" errors for Script listener


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 (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: 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 - Read timed out
2020-01-31 02:45:40.020 ERROR - Class:, 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?

1 answer

1 accepted

0 votes
Answer accepted

Hi Alex,

We're working on a couple of different changes to our infrastructure that should reduce the number of these errors that you see. It is something we are actively working on.



@Jon Bevan [Adaptavist] , ok, that's good, but in the meantime, we are having missing and incorrect data in our Jira instance which is causing people to lose trust in the system.

What's our workaround? Should we move our scripts to a more powerful external provider e.g. AWS?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events