Under Community Review

Hi James,

Thanks for your input to help make SDL TMS a better product. We've recently fixed an issue with the Archiver to make it a little more robust if there are any problems with database connectivity or plugins timing out; perhaps that will help alleviate this problem for you. Do you have any specific examples of Archiver being "finicky" because ideally we would need to raise them as defects and fix them under the normal customer satisfaction channel.

Thanks,

David

Make ARCHIVER less finicky

Tons of plugins and processes hinge on the Archiver being robust, so when the Archiver has a hiccup or goes down, many downstream processes are affected.

Are there ways to make the Archiver more robust?

Perhaps it can be run in a protected process, or some other means to ensure it’s more robust? Perhaps there could be better logging or notifications for when it does go down, so downstream effects are minimized?

It just feels that that Archiver is pretty key to a lot of things, and breaks a lot of downstream functions when it’s not working correctly.

James Hom