Fix 502 errors on container restart and expand API authentication

- Handle 502 Gateway Timeout errors by clearing invalid sessions
- Add graceful session validation failure handling in fetch-thread API
- Expand x-tag authentication to accept additional valid token
- Add debug logging to berth-related API endpoints
- Document the 502 error fix in email system documentation

server/utils/nocodb.ts

@@ -106,9 +106,19 @@ export const updateInterest = async (id: string, data: Partial<Interest>) => {
     });
     console.log('[nocodb.updateInterest] Update successful for ID:', id);
     return result;
-  } catch (error) {
+  } catch (error: any) {
     console.error('[nocodb.updateInterest] Update failed:', error);
     console.error('[nocodb.updateInterest] Error details:', error instanceof Error ? error.message : 'Unknown error');
+    
+    // If it's a 404 error for a newly created record, provide more context
+    if (error.statusCode === 404 || error.status === 404) {
+      console.error('[nocodb.updateInterest] 404 Error - Record not found. This might happen if:');
+      console.error('1. The record ID is incorrect');
+      console.error('2. The record was just created and is not yet available');
+      console.error('3. The record was deleted');
+      console.error('Attempted URL:', url);
+    }
+    
     throw error;
   }
 };