AD LDS – AutoFillBehavior inconsistency in schema (4384013)

Getting error while reviewing the AD LDS schema:
[1777376] Unable to run method (Insert) for object (D87224) because not all mandatory properties are defined.
Missing: nTSecurityDescriptor, objectCategory

Seems like the attribute 'AutoFillBehavior' for the attribute nTSecurityDescriptor shows different values depending on the stage.
In one instance it is displayed as “Never” (DEV), while in another it is shown as “Always” (PROD). 

This appears inconsistent. 

Detailed error seen in JobService.log:

026-06-08 18:44:40.7241 DEBUG (SqlLog f8f5f36c-a432-4ca1-9ccb-439915851477 ) : (49 ms) - declare @JobsToUpdate QBM_YJobStateInfo
insert into @JobsToUpdate(UID_Job, NewState, SuccesInfo, MessageString)
values ('d0c6dc0f-8202-40bf-b98a-5f8159b0950f', 'FINISHED', 0, N'[1777018] Error running synchronization project (LDAP GAAD)''s workflow (Provisioning).
[1777124] Error running synchronization step (gaadAccount) of synchronization configuration (Provisioning (Provisioning)).
[1777376] Unable to run method (Insert) for object (R65658) because not all mandatory properties are defined.

Configuration issue

The DEV connector was built from the generic LDAP connector template, not the AD LDS connector template. The generic schema loader does not understand AD LDS-specific schema flags and defaults AutoFillBehavior to Never for binary attributes like nTSecurityDescriptor. The AD LDS-specific schema loader reads the schema partition correctly and sets it to Always. This is why every schema update in DEV persistently resets the value — the wrong schema loader runs every time.

Build a new connector using the AD LDS connector template.