This is an emerging issue. We will have a fix for this in EPO 5.0.1 when it is available. If you cannot wait for that you can contact support and open a service request to get a POC released to you which will address the issue in EPO 5.0.0. The immediate workaround is to upgrade all agents to MA 4.6 or higher where you will not see the issue.
A KB is in the works but it has not been published yet.