Scheduled Database Connection Point not Triggering

gaston-gledhill

A Database Connection Point that was set to call to a database stored procedure has stopped triggering, with no known cause.  No errors are listed in the ION Grid, Data Flow, or the Enterprise Connector.  Restarting the data flow does not appear to help the documents come through.

ION stops polling or executing the database SQL stored procedures until ION Services is restarted 

Legacy Contributor

This sounds likes either a defect or a local condition causing this, and there isin't enough information to determine which one it is. Particularly, the recurrence pattern is not clear. Once you restart the grid services, at what point do the errors happen again? Is there a pattern? 

Only product functionality that may influence this behavior is the "Pause Connection Point" functionality. Was this connection point ever paused? And have you resumed it? After resumption is the status correctly showing in the Active Connection points screen? 

Other angles are to look at it from the DB side. Have you considered the data volumes at play? Is your query returning a very large amount of data? What is your DB side logs saying? 

And finally, what is the version of your EC? Please make sure its running on the latest EC version. If not, upgrade and see if that solves the problem. 

When none of the above pointers work, please log an incident. Hope this helps.