Receiving SocketException: Socket closed error in JIRA Service Desk Project Automation?

[Ferdy Kurniawan]

Hi team, 

Currently I have setup some project automation within my JIRA service desk project, some of the automation includes auto assignment for tasks created, notifying user about breached SLA through Slack, and task reminder. It has been running without a problem for months but today I receive `SocketException: Socket closed` error for all of my automation when it is triggered. Could you please elaborate on what this error means and what steps do I need to take to resolve this error? Below are some of the error shown in the automation logs. 

No subsequent actions were performed since JQL condition did not pass due to error running JQL:"(key IN (FIPSS-425) AND (priority = highest AND status = "Waiting for support" AND ("FIPSS Request/Issue Type" IN ("Routing Issue") OR "FIPSS Request/Issue Type" IN ("Routing Request"))))" - SocketException: Socket closed

Error running JQL search to find issues breaching SLA:SearchErrors{jql='(cf[10027] > 30m and cf[10027] < 37m) AND (project in (16625))', errors=SocketException: Socket closed}

No subsequent actions were performed since JQL condition did not pass due to error running JQL:"(key IN (FIPSS-425) AND ("FIPSS Type of Routing Request" = "Add New Airline"))" - SocketException: Socket closed

thanks!

[John McKiernan]

Hi Ferdy,

thanks for your message. These errors can be quite intrusive and annoying alright but the rule should still be running. 

We have an existing improvement here to make these errors 'ignorable' https://codebarrel.atlassian.net/browse/AUT-1375

If you are experiencing any issues with your rules firing, shoot through a support request and we can take a look into it!

Cheers,

John 

[Deleted user]

I received this error on several rules at the same time today.