Anyone else having issues with the web request headers in server side workflow 5?

I have a workflow that sends a web request and when I run it in server side workflow 5 it returns an unauthorized response. I have tested the same exact module in the client side and it works perfectly executing the request and returning a success message. From what I can see it looks to maybe be an issue with the headers but I'm not sure why as they are the same for both client and server side. Below is the the response, minus the bearer token which I have manually removed for security issues.

{

 "results": [

  {

   "$type": "JobResult",

   "outputs": {

    "Response": "Unauthorized",

    "Options": {},

    "Headers": "bearer [Removed Token for Security]"

   },

   "tag": "c32ecde11ebd4547acccce654d08080b",

   "url": [Removed URL for Security]

  },

  {

   "$type": "JobQuit",

   "kind": "Run"

  }

 ],

 "log": {

  "start": "2019-04-01T23:20:26.5894305Z",

  "end": "2019-04-01T23:20:26.5933233Z",

  "traces": [

   "Information: 0: Logs: [Removed URL for Security]"

  ]

 }

}