AEM 6.2 OSGI component state does not stay Active Hi,We have a process in which our AEM 6.2 authoring server needs to perform a nightly backup. We notice that on the next day the 2 OSGI components that we need to publish content will have these states:ActivateListener (to decide what type of content to publish) - may be satisfied or activeConfigurationService - activeIs satisfied the same as "resolved" in an OSGI component life cycle? Is there a difference between satisfied and active - it seems that if things work correctly, the ActivateListener will proceed whether in a satisfied or active state.What we have also noticed that in publishing a piece of content, the ActivateListener may before publishing be satisfied and then change to active upon publishing. Likewise, it can be active before publishing, then changes to satisfied.Does it mean that the ActivateListener is not stable? Is there some other way beside looking at /system/console/components to determine if a component is truly in an "active" state? Should we expand each