- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
IGL 7.1.1 Scheduled collectors not running
Anyone had/having issues with scheduled tasks not executing as expected - either collectors or custom workflows?
Noticed one of our ADCs had not run since it was imported into our live environment a couple of weeks ago but when you examine the details it says it is scheduled. It's not an issue with all the others, only this one. Weird.
- Tags:
- Community Thread
- Data Collection
- Discussion
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- IG&L
- IGL
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
If you have a support case open I will defer to them for a resolution.
Note that for Collectors scheduled with the default scheduling option (except for the initial schedule) the next scheduled collection run is added to the scheduler as part of the completion process for the last scheduled run. It is possible somehow the initial scheduler entry was not created for this collector. You might try deleting the schedule and creating it again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
How are you scheduling your collector?
- Under Collectors/Scheduling
- From a Custom Task Workflow
- From an external cron job using Admin API WebServices?
You say the problem also affects "Custom Workflows". I am not aware that you can schedule normal workflows. Do you mean "Custom Tasks"?
There are some issues with Custom Task workflows interfering with the scheduler. Specifically there are some issues if you rename or delete custom task workflows that have schedules. These are resolved in all current patches but it is possible to have corrupted data from previous versions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Ian Staines Most recent example was an ADC attached to an application where the scheduling information on the collector was marked as Yes with a suitable schedule (and yes, we have a case raised with Support), however I have also noticed incidence of Custom Tasks not running as scheduled.
We don't run our collectors via any other route - only using the OOTB options.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
If you have a support case open I will defer to them for a resolution.
Note that for Collectors scheduled with the default scheduling option (except for the initial schedule) the next scheduled collection run is added to the scheduler as part of the completion process for the last scheduled run. It is possible somehow the initial scheduler entry was not created for this collector. You might try deleting the schedule and creating it again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Were you able to resolve your problem? I could not identify a support case open for this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Yep. I believe one of our Support team removed the scheduling then reapplied it, which appears to have resolved it.
