Not here error appears briefly when enabling features

src/pages/workspace/FeatureEnabledAccessOrNotFoundWrapper.tsx

@@ -44,7 +44,8 @@ function FeatureEnabledAccessOrNotFoundComponent(props: FeatureEnabledAccessOrNo
     const shouldShowNotFoundPage = isEmptyObject(props.policy) || !props.policy?.id || !isPolicyFeatureEnabled;
     const shouldShowFullScreenLoadingIndicator = props.isLoadingReportData !== false && (!Object.entries(props.policy ?? {}).length || !props.policy?.id);
 
-    // If the feature is pending, we should not update the feature state
+    // If the feature is pending, we should not update the feature state.
+    // This is due to that during the creation of a workspace the feature state changes several times while we are waiting for a response from the backend, what unexpectedly causes 'Not Found' to be shown.
     useEffect(() => {
         if (pendingField && !isOffline && !isFeatureEnabled) {
             return;

src/pages/workspace/WorkspaceInitialPage.tsx

@@ -186,7 +186,8 @@ function WorkspaceInitialPage({policyDraft, policy: policyProp, reimbursementAcc
 
     const protectedCollectPolicyMenuItems: WorkspaceMenuItem[] = [];
 
-    // If features are pending, we should not update feature states
+    // If features are pending, we should not update feature states.
+    // These changes are made to synchronously change feature states along with FeatureEnabledAccessOrNotFoundComponent.
     useEffect(() => {
         setFeatureStates((currentFeatureStates) => {
             const newFeatureStates = {} as PolicyFeatureStates;