Delay (in milliseconds) between successive content registration API calls to ActiveEfficiency. Registrations can fail when ActiveEfficiency or the SQL Server hosting ActiveEfficiency DB is busy, overloaded or down for maintenance, resulting in content registration mismatch between the clients and ActiveEfficiency.

The Content Registration Sync Cycle is available in Nomad 7.0 or later (1E Client 4.1 or later) which registers pending and failed content registrations with ActiveEfficiency. Please refer to Single-site download: Improved resilience of content registration.

Registry valueTypeDefault valueNotesInstaller property


Delay, in milliseconds, between successive content registration API calls to ActiveEfficiency

Range: from 100 milliseconds to 60000 milliseconds (1 minute).