Issue Summary

In the previous infrastructure, whenever a request got disconnected (for example, due to a change in the "Request Type" field to a not connected request type), if we reverted the "Request Type" field value to a connected request type, the request would reconnect to Slack normally.

With the new infrastructure, in case a request gets disconnected once, even if the "Request Type" field value is changed to a valid request type, it won't reconnect again.

Steps to Reproduce

• Create a request on Slack using the Assist bot (any method).
• In the Issue View, update the “Request type” value to a request type not connected to JSM Chat.
• This will make the “This request is no longer connected…” message appear.
  
• Revert the “Request type” field value to one connected request type.

Expected Results

• Once a valid "Request Type" value is set, the request should be reconnected in Slack.

Actual Results

• The “This request is no longer connected…” message continues appearing and the request is not reconnected.

Additional notes:
It was observed that changing the "Request Type" field value without changing the Issue Type AND the "Request Type" is connected to the Request Channel it won't disconnect the request.

But in case there is a Issue Type change, or a not connected request type is set, this will cause the disconnection.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.

Refrain from updating the "Request Type" field value, unless it is using the same Issue Type and the "Request Type" is connected to the request channel.