I thought this had just been a weird anomaly but we’ve now seen evidence of it happening four times and each time it’s causing problems.
For some reason that we cannot seem to explain, we are seeing relationship fields just suddenly lose their app configuration. I added a relationship field yesterday, configured it against a particular app (this one happened to be within itself, but my other examples didn’t work like this) and then come back today to find that the field has zero apps registered against it and we did nothing to make this happen.
Could someone please look into this?? I’m happy to supply App and Field IDs!
That does indeed sound super strange, we’ve never come across a case where a relationship field just suddenly loses its app configuration on its own. But if you’ve already seen it four times, then clearly something’s not working as it should.
Since relationship fields are such a core part of the system, we definitely want to get to the bottom of this as quickly as possible. Could you please send me the App ID and Field ID via DM so we can dig into the details and check for patterns or issues on our side?
Really appreciate you raising this and sorry for the trouble it’s caused. Hopefully we’ll be able to identify what’s happening soon! I’ll keep you updated once we know more.
you’re absolutely amazing! Thanks so much for the video!
We had already spent quite some time on this issue and had API field updates in sight as a possible cause and were investigating those, since we never had an issue like this before. But we just quickly verified - and yes, since updating field slugs is a new feature, it seems that’s exactly what’s causing Andrew’s issue.
Thanks a ton for your insights. We’ll jump right into fixing it now. Really appreciate your feedback and help!
