Are Indicator Tasks ever cancelled automatically by OOTB logic?

[Mira1992]

Hello community,

I am using Control Indicators, and I've encountered an issue where some Indicator Tasks are created directly in the Cancelled state.

The tasks are being generated by the OOTB scheduled job:

GRC Indicator Nightly Run → new IndicatorEngine().runAllIndicators();

I haven’t customized the indicator task creation logic — it’s all out-of-the-box.

What I’ve Tested So Far:

• I confirmed that the task is inserted with state = 7 (Cancelled) right from the beginning (verified via sys_audit).

• The associated Indicators and Templates are active.

• Some Indicator Templates have an empty due_date_duration — but this alone does not consistently lead to cancellation.

• I added logging in the overridden ManualIndicatorStrategy.createIndicatorTask() method, and confirmed:

  • The task is being created with or without a due_date

  • Nothing in my logic sets state = 7 post-insert

• I reviewed Business Rules that adjust the due date, but none of them cancel the task.

• When I manually trigger the same Indicator using Execute, or re-run the scheduled job for the same Indicator, the task is sometimes created correctly.

What I Want to Know:

Is there any out-of-the-box logic in the GRC platform (e.g., background job, async rule, Script Include, etc.) that would automatically set an Indicator Task’s state to Cancelled upon creation, possibly due to missing or invalid fields like:

• Empty due_date

• No assigned_to

• No opened_by

Any pointers to the relevant logic or confirmation of expected behavior would be greatly appreciated.

Thanks in advance.