Indicator Task not running

[Alfredo6]

Hi! I have several questions hoping you guys can help..

We have activated the GRC module to automatically generate tasks based on indicators that trigger the compliance status in the Control.

However I have identified that the Indicator Task will run but will not update the "Next Run" Time if it doesn't has a value in the "Table" field from the "Collect Supporting Data", even though that checkbox is false. Is this how it is supposed to be or is it a problem?

Also, is there a way to update the OOB script? I've seen that Indicator Task won't run if the Control is Non-Compliant, and we require to keep asking for Deliverables on a regular basis, we use the Indicator Tasks for the user to submit these Deliverables, but if an Issue is still open, then the Task will not be created.

Thanks!

[ian_cox]

Alfredo,   I'll see if I can get you some help with this.

[vinothkumar · Accepted solution]

It is a known error and it was fixed in Helsinki Patch 9.

Helsinki Patch 9

[paulgerts]

Hi Alfredo,

I've had the same issue with several clients.

As it turns out, the job responsible for collecting those indicator scores is turned off by default. As soon as you set this job to 'active', the indicators will start collecting data.

You can find the job in the "Scheduled Jobs" menu item, the job name is "GRC indicator nightly run". As you will see, the active flag for this job is set to 'false'. You can manually set this to 'true'. This will automatically run the job at midnight.

The fix in Helsinki Patch 9 is probably doing the same. But you don't have to wait for that...

Please let us know it that fixes your problem!

Cheers,

Paul

[Alfredo6]

Thanks Paul,

The active flag in the job caused some pain at first, but the main problem is that the new IndicatorEngine().runAllIndicators(); script will prematurely error and the next run date will not be set if there is no "reference_table" for the supporting data in the indicator, even though the indicator does not require support data gathering.

As I see in the Helsinki Patch 9 notes, this is fixed.

Best regards,

Alfredo