Knowledge Base

Syncing Subscriptions and Plans

Subscriptions associated with a particular plan are synchronized, or
synced, with it: any changes made to the plan are automatically
applied to all its subscriptions. This is true for both service and
add-on plans.

In case a plan offers a privilege which makes it possible for a
subscriber to change a particular resource or service, this
resource/service allocation is not synced. For example, if a
subscription provides the privilege of DNS zone management, then the DNS
zone settings of the associated service plan are ignored during
synchronization.

States of Subscription

Plesk allows the following deviations from the default subscription
state (active and synced with the service plans):

Locked state, which means locked for syncing, indicates that a
subscription is excluded from syncing with the associated plans.

A subscription gets locked if you change the parameters of the
subscription, without changing the associated service plan. Such
locking secures your customizations so that they are not overwritten
the next time you change the plan and all its subscriptions are
synced.
Unsynced state indicates that some services or resources offered
with the associated plans cannot actually be provided with the
subscription.
Suspended state. This state is not related to the synchronization
of a subscription with the service plan, but it affects the behavior
of websites. Plesk suspends subscriptions automatically if their
expiration date passes. In addition, you can suspend a subscription
manually.

Note: If a plan offers a privilege that makes it possible for a subscriber
to change a particular resource or service, this resource/service
allocation is ignored during a sync. For example, if the plan
provides the privilege of PHP settings management and a customer
changes some PHP setting, its subscription remains synced with the
plan (even if a value of the PHP setting in the subscription differs
from the corresponding one in the plan).

Unsynced Subscriptions

Plesk does not check whether a service or a resource that a service plan
should provide is actually available in the system. For example, when
creating a plan, you can select to provide Perl support when
mod_perl is not installed on the server, and Plesk will let you do
it and will show no error or…