Task server not using configuration changes

What is your full version number? Plugin enablement/configuration changes prior to 12.1 depended on the Plugin Synchronization job (which is scheduled to run every 60 seconds by default but is subject to other jobs running within the current node--this one runs on each application node). In 12.1, invalidations are pushed through the message bus and should occur almost immediately (pending other nodes processing plugin initializations since only one node can initialize at a time).

Regarding email, any email that is queued to be sent will still be sent after disablement but new email will not be queued. Email will be sent with the latest version of the email configuration.

What is your full version number? Plugin enablement/configuration changes prior to 12.1 depended on the Plugin Synchronization job (which is scheduled to run every 60 seconds by default but is subject to other jobs running within the current node--this one runs on each application node). In 12.1, invalidations are pushed through the message bus and should occur almost immediately (pending other nodes processing plugin initializations since only one node can initialize at a time).

Regarding email, any email that is queued to be sent will still be sent after disablement but new email will not be queued. Email will be sent with the latest version of the email configuration.

Hi Ben    this was for 12.0.5.20244 but in older versions of 12 and 11 we have seen times when we had to restart the job service if plugin config has been changed and was used in jobs, so email digests for example

Some configuration that is not plugin-based could take longer. For example, email configuration and other "Site" options are updated every 5 minutes. In 12.1+, these, too, are forcefully invalidated using the message bus.