Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Community showcase

All you wanted to know about customer support KPIs

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...

107 views 1 5
Read article

Community Events

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

Events near you