How to make an external API call from a processing screen

Hi @JWS539 

Am using the below code and have not faced any such kind of issues. Please review once.
 

 public static HttpResponseMessage RestAPIRequest(token, string apiUrl, string method, string data)
        {
            HttpResponseMessage response = new HttpResponseMessage();
            try
            {
                HttpClient cl = APIHeader(token, apiUrl);
                var response1 = cl.GetAsync(apiUrl);
                response1.Wait();
                response = response1.Result;

            }
            catch (Exception)
            {
                response = null;
                throw;
            }
            return response;
        }


  private static HttpClient APIHeader(string token, string apiUrl)
        {
            try
            {
                HttpClient cl = new HttpClient();
                cl.BaseAddress = new Uri(apiUrl);
                int _TimeoutSec = 300;
                cl.Timeout = new TimeSpan(0, 0, _TimeoutSec);
                cl.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
                cl.DefaultRequestHeaders.Add(KNMCConstants.Authorization, “Bearer  “+ token);
                return cl;
            }
            catch (Exception )
            {
                throw;
            }
           
        }

Hi Jini N,

I reviewed and tried your code, and got the same result (the processing form ran for approx 19 of the 44 records and then the “Server has restarted” message pops and the form hangs.  See below for the modified code with the changes you suggested:

Only change I made was hard coding the token in APIHeader.  Can you see anything obviously wrong here?

I don’t doubt your code works, and mine did in R2021, just not R2023.

My suspicion is that there is nothing wrong with either sets of code but some issue in the build.  Not sure where to go from here.  Any suggestions?

We have had quite a bit of trouble with customisations that work in R2021 but not R2022.  Even now we are having to apply workarounds.  One such example is that unless we add the below to Web.Config we can’t get the simplest customisation to even publish on a local environment:

<add key="CheckCustomizationCompatibility" value="False" />

I wonder whether the code would run on a live site without any problems.  Might be worth a go but doesn’t make debugging/trouble shooting easy.

Any other thoughts on places we could go next to get a resolution greatly appreciated!

Thanks,

John.

Hi Jini N,

Thanks for the extra info.  I didn’t even know these tools existed, they look quite useful.  Had a look though and they didn’t shed much light on the problem.  The first and only exception logged was “The server has restarted”

Will contact support as suggested.

Thanks again for all your help,

JOhn.

Hi @JWS539 were you able to find a solution? Thank you!