Discussed with Arvin the error encountered in the web application, as per Arvin, the first error has been fixed when the JDA DNS is changed into IP in the config, but after fixing new errors are received. Checked the concern with Arvin, as per checking, the cause is the communication link failure, checked if there are more config in the web application that is used, and as per checking, there is a changed the host on it as well, from DNS into IP, then tested it again, as per checking, the error is still encountered, checked if there is cron processed that did not finish, as per checking, there is, remove the lock file which consists of PID to re-execute the cron job again, as per re-execute, an error is encountered, communication link failure, check for other config and change the host as well, after changing the host in .env, executed the job again and checked the portal, as per checking, the error is gone. Arvin advised the user to check it on their side and received feedback that it is now OK.