Archive rule is not functioning

[jayachandra1]

we are implementing Archive functionality for Incident,Change, Request, Problem, KM.

initially we have started with Incident, for testing purpose we have defined Archive rule for "Before 2hr from the closed" :

But incidents are not achiving, i just check the Scheduled job for "Archive", it is in "Ready" state, the next action it is showing as "2017-10-31 14:00:00".

i guess this scheduled job is not executing, since the archive functionality is not working, below is the snapshot of "scheduled job:, this job is defined with Triggered Type is "On Demand".

can someone help me how to make this job run or how to make the Archive functionality work properly.

Thanks and Regards,

Jay

[Rajendra Bagade]

Hi jaya,

For implementing the Archive functionality, you need to activate plugin 'Data Archiving'.

Once the plug is activated,

Verifying that the archive rule is selecting records as expected, activate the archive rule. By default the instance runs the archive rule as a schedule job set to run every 60 minutes.

Navigate to System Archiving > Archive Rules.

Select the archive rule you want to activate.

Select the Active check box.

Click Update.

Activating an Archive Rule Immediately

If you do not want to wait for the scheduled job to run the archive rule, you can manually start the archive rule.

Navigate to System Archiving > Archive Rules.

Select the archive rule you want to run.

Click the Run Archive Now related link.

PS: Hit like, Helpful or Correct depending on the impact of the response

[jayachandra1]

Hi Rajendra,

Thanks for the information.

However Plugin "'Data Archiving'' is already active, archive rule difined with below condition for testing purpose, which is supposed to archive the inactive incidents and closed date is before last 15 min.

i created an incident and closed, waited for 15 min and had run the Archive rule manually, but entry creating under archive run with no data, the primary count is '0'.

this means the archive rule is not archived the incident data.

can you suggest if there are anything missing or misconfigured.

below is the snapshot:

Archive run data for this Archive rule:

Thanks and Regards,

Jay

[Chris M3]

Check to make sure you don't have two rules for the Incident table.   There is an issue with the archive functionality (no projected fix) that will sometimes confuse the system if there is more then one rule.

[jayachandra1]

Hi Chris,

I have verified and found there is only one Archive rule on Incident table, but still incidents are not Archiving as per the configuration.

Regards,

Jay