Question
1
Replies
221
Views
PEGA
Posted: December 12, 2017
Last activity: December 13, 2017
Closed
Handling scheduled agent down time
We have a requirement where we use an agent to load data from legacy source periodically.
Lets say - Agent1 runs for every 60min to load new data from a DB table from Legacy system which we cannot edit. (read only access)
If the DB was down for 80 min (from previous agent run) for some reason, How Agent1 will be able to load that data for the 20 min?
Is there a design pattern for this? Is it right to maintain a property that keeps track of the last successful run and allow agent based on that?
***Edited by Moderator Marissa to update categories***
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
I'm not aware of a way for the agent schedule itself to handle this. It seems like you would need to have the first step in the agent activity do something to see if it should continue with the remainder of its normal processing steps (whether it be time based or checking to see if it's able to connect to the external DB or however you wanted to do it).