I’m running into an issue with the users collection and the authenticated user object in FlutterFlow.

I’m using Firebase Auth with the default users collection that FlutterFlow creates.
The user document initially has the default fields (display_name, photo_url, etc.) and some custom fields I add from the app UI (let’s call them p, q, r).
On the backend, I also have a Cloud Function triggered on user creation, which adds additional fields (x, y, z) to the user document.

Here’s the problem:

In Firestore, the document looks correct: all fields a,b,c,p,q,r,x,y,z are there.
But in the FlutterFlow app, after the Cloud Function runs, only the default fields are visible in the Authenticated User object.
The custom fields (p,q,r) I added earlier from the app are no longer available in FlutterFlow, even though I can see them in Firestore.

So it seems like FlutterFlow only maps a subset of fields(default ones) when the user doc is updated via backend code

Is there a way to force FlutterFlow to always sync/refresh the schema of the users collection, so new fields (p,q,r,x,y,z) are visible without manual refresh?
Or do I need to initialize all custom fields upfront when the user is first created, so FlutterFlow knows about them from the start?
Any best practices for handling backend-updated user fields so they remain visible in the authenticated user object?

Most importantly i would like to know if flutterflow allow's user collection to be updated from backend? or is it strictly schema mismatch?

Thanks in advance 🙏