Check event registry – make sure the retro events are active.

If you search on Retro – RetroAddlPay and RetroPayJobChange should both be returned in the search.
Make sure the event status is ACTIVE. By default, the logging enabled switch will be turned OFF, but log
entries should appear if the event processing failed. Turn on logging if you want log entries for all
events whether successful or not.
The delivered Application Package event handler is PY_RETROPAY_EVENT
The RetroMethods application class is the “parent” class. It is extended by two other application
classes. RetroMethods contains common methods that are used by the other classes.

JOB retro changes will invoke the primary ProcessEvent method from UpdateRetroPay application class.
Where necessary, the UpdateRetroPay application class will execute methods from the RetroMethods
application class.

Additional Pay retro changes will invoke the primary ProcessEvent method from the UpdateRetroAddlPay
application class. Where necessary, the UpdateRetroAddlPay application class will execue methods
from the RetroMethods application class.
TROUBLESHOOTING:

Check the Event Monitor:

You need to know the date and time the event occurred in order to look up the event. When you find
the event, click on the Handlers link.
If the event is in X status, you can drilldown on the exceptions link for more information.
The Event Monitor only logs exceptions that the Event Handler or Event Framework is specifically coded
to detect.

There may be more information on the error in your Application Server log.
TROUBLESHOOTING:

If nothing shows up in the Event Monitor, elements of Integration Broker may be missing or not running,
or the configuration may be incorrect.

Make sure Domain Status is Active

Make sure your node is Pingable.
Make sure EOEN_MSG_CHNL queue is Running
Make sure you can ping your LOCAL gateway.
Search for a Routing that has Service Operation EOEN_MSG defined on your node. The name of the
routing may vary, but it must be active.
If the routing does not exist, you can generate it from the Service Operations setup. Look for Service
Operation EOEN_MSG

Make sure Service Operation is Active, and Local-to-Local routing exists. If it does not, you can select
the regenerate Local-to-Local checkbox and Save.

Note the warning message that Regenerating will set all routing field values to their initial state.
Also note the EOEN_USER Role must be defined on the User Profile.