Archive Rules not working properly

[Pratiksha2]

Archive run state is remains active for some archive rules. Please see the screenshot below.

Thanks in advance.

[Community Alums]

Hi Pratiksha,

Make the changes in glide.db.archive.chunk.max.process.time  system property:its a integer value by default its 600000, you can make the change here.

Number of milliseconds a record can remain in the Active state in the [sys_archive_run_chunk] table. The time is the difference between the system time and the value of the Start field in the [sys_archive_run_chunk] table.

Rules to prevent the archive process from consuming too many system resources have been automated. You can manually change the system behavior.

Beginning with the Quebec release, rules to prevent the archive process from consuming too many system resources have been automated and the glide.db.archive.max.rule.records property is deprecated. It is no longer necessary to adjust these properties.

By default an archive rule follows these processing rules:

• Archives 100 records for each batch job
• Sleeps one second between batch jobs
• Runs 10 batch jobs in an archive run

Note: The archive and destroy properties listed in the table are not used if the [sys_archive_run_chunk] table is deleted.

To manually control how many records the archive rule and destroy processes at one interval, you can change these default settings by adding the following system properties.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Pratiksha2]

Archive run state is stuck to the active . Now its been 2 nd day but still it is not completed. What is the reason behind it and resolution for this issue?

[Supritha Monap1]

Hi Pratiksha, 

I am facing similar issue. Could you please confirm if the root caused was found and what it was?

Thanks!