Skip to main content
All CollectionsTroubleshootingComparisons
Is your Flow not showing up in the Flow Navigator mode in our comparison?
Is your Flow not showing up in the Flow Navigator mode in our comparison?
Mateusz Kochanowicz avatar
Written by Mateusz Kochanowicz
Updated over a week ago

It may happen that when you're trying to preview a specific Flow in our Flow Navigator mode by selecting this icon on the comparison results page, Gearset returns a message saying:

"Gearset encountered an error while processing your Flow:

Could not render auto-layout Flow since there are overlapping elements. You can fix this by using the Salesforce Flow Builder to change the Flow from auto-layout to free-form and back again, then saving the Flow."

Explanation of this issue

The reason why it may not be possible to display your Flow correctly in Gearset can be due to your XML stating bad locations for elements.

This might happen if there was a direct edit made to the XML file of the Flow (e.g. through edits made directly in the Git branch), or when location changes haven't been deployed between orgs.

It's possible the XML incorrectly states that the Flow is in "auto-layout" viewing mode, which may be invalid if the same Flow in the Salesforce org is identified as being in the "free-form" viewing mode.

In such case, Salesforce may ignore the "auto-layout" property in the XML if the elements are wrongly placed.

Note: If your Flow is in the "free-form" viewing mode in the Salesforce org and the Flow's XML is matching that setting, you should never run into the above error.


Resolution

If the intention is for the Flow to be in the "auto-layout"

Follow these steps:

1 - Change the viewing to “free-form”, and back to “auto-layout”.
2 - Save the Flow in the org in “auto-layout” viewing mode.

This should fix the positioning of the elements both in Salesforce and in Gearset.

Once you re-run the comparison in our app, you should be able to preview the Flow in our Flow Navigator.

If the intention is for the Flow to be in "free-form"

Make sure that the Flow's viewing mode in the org is saved to "free-form".

Did this answer your question?