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 applies to both service and add-on plans.

However, in case a plan offers a privilege which allows 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

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 applies to all kinds of plans: service plans, their add-ons, and reseller plans.

  • Plesk allows for the following deviations from the default subscription state, which is active and synced with the service plans:
  • The locked state, which means it is locked for syncing, indicates that a subscription is excluded from being synchronized with the associated plans.

A subscription gets locked if the parameters of the subscription are changed without changing the associated service plan. This type of locking secures any customizations that have been made so that they are not overwritten the next time the plan is changed and all its subscriptions are synchronized.

  • The unsynced state indicates that some of the services or resources offered with the associated plans are not able to be provided with the subscription.
  • The suspended state. This state does not have relation to the synchronization of a subscription with the service plan, but it does affect the behavior of websites. Plesk automatically suspends subscriptions if their expiration date passes. Additionally, you can also suspend a subscription manually.

Note: If a plan offers a privilege that allows a subscriber to change a particular resource or service, this resource/service allocation is ignored during synchronization. For example, if the plan provides the privilege of PHP settings management, and a customer changes some PHP setting, the subscription remains synced with the plan, even if the 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 on the system. For example, when creating a plan, you can select to provide Perl support, even if mod_perl is not installed on the server. Plesk will allow you to do this and will not show any error or warning messages.

A subscription will be automatically marked as Unsynced if Plesk is unable to provision the resources and/or services defined by the plan. This can happen in the following cases:

  • When the subscription is created.
  • When the properties of the associated plan are changed.
  • When an add-on plan is added to or removed from the subscription.