I had a similar issue - it was due to the fact I was authenticating into Guide via SSO to OKTA and not through their new V2 auth. 

By signing into Guide with my password, I was able to see all of my missing custom fields.

@willpatterson - that must be it.  I use Okta as well.  I’m not sure if I even know my password - its locked away in Okta

Is this something that is going to be fixed - or can we just not use Okta any longer?

Great question - i’m not sure! But I do know engineering is aware of it. I was chatting about it with support this morning. 

I have OKTA still setup - but I temporarily have Strict Mode disabled, which allows me to sign in either way.  I had to reset my password in Guide this morning because I had no idea what I would have used originally before setting up OKTA lol @jjmcdev 

Hi @jjmcdev , in addition to the great insights shared by @willpatterson , any time you feel you are seeing behavior that you don’t expect, please report that in to our Technical Support team via your in-app chat bubble.  As of 4/24/24, the new custom fields (Custom Fields V2) is in a closed beta. You should not see any existing custom fields disappear whether you’re in that closed beta or not, so if you’re still seeing this, please report it in.  Thank you!

Jumping in here real quick to clear up any confusion!

This channel is for closed beta so please continue using this group to share any unexpected behavior with beta features.

In this case you are right (@jjmcdev) to share your findings so @chrishaleua is made aware! 

If this was a feature available to all (i.e. My templates aren’t loading), then @bobm is right in his direction to chat with Technical Support.

Sorry if this is redundant, but I just wanted to draw that distinction!

Carry on!