Hi @RiSpence
Which FSM version are you using? If it’s an old version, this could happen due to the expiration of the integration monitor person_id expiration in your respective environment. Just search the app param INTEGRATION_MONITOR_PERSON_ID (if it’s null, then it has to be the METRIX person_id) and then check whether the password has been expired under the security tab of the person screen. You may need to give a full cache refresh after changing the expiration date.
Give this workaround a try, if the previous suggession did not work out for you.
Hi Richard,
besides checking the Integration Monitor Person and Password parameters, you could also check the last ping received from the default Intergration Monitor instance (Screen: Integration Monitor Instances). If nothing of the above helps, you can try to disabled and enable the Schedules and doing a refresh schedules and re-start Integration Monitor in between. Sometimes this can be a bit tricky when the schedule is out-of-sync.
Best regards
Roman
Hi Roman. Everything with the integration person record was fine and the last ping was more or less current. In the end, I think it was the disable, refresh and restart sequence that got things going again but I still had to wait until the time caught up to the next run time which was several hours. I would have to think that a mechanism similar to the ability to actually set the next run date on the scheduled processes would be helpful as well for the Integration Schedules.
Cheers,
Richard