Solution

Now here, we new that the server and the architecture of the server was able to handle the load only if we completely optimize the way we retrieved the records from the API. We stopped multiple hits from being made on the server and simply ran a check for the updated content using ids. Now only the activities and events that were updated were fetched but even then, remained the problem from the api. The API would not respond at times which is when we would send responses to the api until the api completely responded to the requests that we sent. This is where the problem was resolved and all the records were completely retrieved from the API. The problem usually lies in the systems that we integrate but this taught us that even if the APIs are faulty or not completely made perfect, the developers can still work on their end to optimize the process and retrieve the information that is necessarily needed.