Before this update, reconciliation timeout values configured via the extraConfig field (which propagates to the internal ConfigMap) were not correctly mapped to the operator's environment variables. This was particularly evident when timeout.reconciliation was set to 0. The update ensures the timeout.reconciliation field is explicitly mapped to the appropriate environment variable in the operator's deployment logic. The operator now correctly recognizes and applies these user-defined timeouts for consistent control over sync cycles. Key Usage Notes While this fix improves the reliability of the extraConfig mapping, please be aware of the following implementation details: Manual Restart Required: If you apply these settings via extraConfig, the change is propagated to the ConfigMap, but the StatefulSet controller will not automatically pick up the changes. You must manually restart the controller for the new timeout values to take effect. Recommended Approach: For a more seamless experience, it is highly recommended to use the controller.appSync field. Using this field allows the operator to manage the synchronization logic more natively without the limitations associated with manual configuration overrides.