As discussed via the other thread, we decided to forgo
Bug 22114 - Expose external account polling interval in UI because of the server performance effects -even if you set a min you might not be prepared for the consequences; however you can vote for
Bug 21199 - add ability to set autopolling in admin console
There's also:
Bug 33151 - data polling interval inheritance issue
Could you
update your profile with version info so I can get to the same repo point as you?
Can you nail down a set of steps? ie: Is it only prior accounts that have difficulty, are new accounts fine from the point you set the cos value?
cc cos
ca user
mc datasourcepollinginterval
ga user > shows fine?
add external account
gds user > does it get inherited right?
vs
add external account to existing cos (without datasource set)
no value shown on ga or gds
mc datasourcepollinginterval
ga user > show fine?
gds user > not inherited?
Quote:
<attr id="455" name="zimbraDataSourcePollingInterval" type="duration" min="0" cardinality="single" optionalIn="dataSource,account,cos" callback="DataSourceCallback" flags="accountInfo,accountInherited,domainAdminMod ifiable">
−
<desc>
The time interval between automated data imports for a data source, or all data sources owned by an account. If unset or 0, the data source will not be scheduled for automated polling.
</desc>
</attr>
|