Star Citizen 3.24.1 - Issue with Landing request and ASOP terminals at Grim HEX.

Issue started after 3.24.1 patch. A few hours before patch 3.24.1 dropped on the servers, a friend and I completed a bunker mission (Using version 3.24.0). We were using my friends Cutlass Black which he flew down to the Bunker mission. After we finished the bunker mission we got into my friends CB and he decided to quit the game for the evening. I then proceeded to head back to Grim Hex using his ship and successfully requested landing and landed his ship in my hangar. I then quit the game (I did not attempt to store my friends Ship in my hangar). Upon return the next day the update had been made available therefore I updated the game to 3.24.1
All was well...Game started fine and I proceeded to the space terminal as I selected Lorville as starting point. Upon arriving at the ASOP ship terminals at the space station on Lorville, I noticed that I had inherited my friends Cutlass Black (as well as having my own Cutlass Black) and he had lost it from his inventory. Thinking nothing of it I claimed a ship (my pledged titan) and headed to Grim to 1. Place my fingerprint and 2. Claim all my ships. I Arrived at Grim HEX and requested landing services with no issues. Landed at Grim and headed to ASOP terminals to claim all my remaining ships (So they were all available at GH). Once all claimed, I proceeded to request my Titan at the ASOP terminal on GH but the terminal hung for around 30 seconds only to be presented with an error stating "This request cannot be completed at this time". I also tried to access my hangar on GH via the elevators but to no avail as the option wasn't listed on the elevator panel. Since then I have not been able to request landing at GH or request any ship from the ASOP terminal. I do seem to be able to claim all my ships at GH via the ASOP terminals but once clamed I cant retrieve any of them to a hangar. If I travel to another station (any) I can successfully claim and request any of my ships and access my hangar therefore this issue only exists at Grim HEX.