Field maps form being slow to load

[KatieQuantrell]

Hi, I have a Field Maps map set up where users can collect new records through adding a point to the map and filling in the associated attribute details in the form.

However today the form has gone really slow to load. Around 8 seconds from clicking the add new icon to show the form, but then another ~10 seconds for it to fully load (with all fields showing their headings etc). If the point is added to the map before the form fully loads (despite it looking to be added to the map) on trying to submit the record an error is shown saying that not point has been submitted, with you then having to update the points location.

This is making the form unusable for users. Please could someone help problem solve what could be causing it to load so slowly. 

Many thanks

[ColinLawrence]

Hi @KatieQuantrell , have you reached out to Support and opened a ticket about this? If not, I would encourage doing that for starters. 

Can you also let me know what device you are using and what version of Field Maps you see this on? When did you start experiencing the problem? Are there expressions in the form?

[KatieQuantrell]

Hi Colin, many thanks for your reply. 

I've tried the app on two devices; a android (Motorola) mobile phone, with version 25.2.7 of Field Maps. And also a Samsung tablet with version 25.2.5 of Field Maps. The form is slightly quicker to load on the tablet but still very slow. 

The form itself, does contain a few calculated expressions, as well as two sets of contingent value fields, but was previously working fine. I first noticed the form being slow on Wednesday (05/11/25). 

Any ideas into what may be causing this would be really appreciated. I will also raise with support (but need my colleague to be back in the office to do this). 

Many thanks

[McKenziGaines]

I've had a similar issue. All devices are iOS on Field Maps version 25.2.5. The form never loads for me, though. I only see a spinning circle forever. The form I'm using does have a calculated expression, required fields, and conditional visibility set as well. I'm not sure if that's causing the hiccup or not. I might have try removing those rules one by one to see if that resolves the issue. 

Thanks for your post! Glad to see it's not just my org. having issues. 

[ColinLawrence]

We have heard of a few reports that already came into Support that sound similar. The team is looking into this.

@McKenziGaines It is probably not a single expression of yours perse but more likely the total amount of them that need to run to load the form. I would expect it to load eventually though so its possible there is a different issue here as well.