Thanks Scott and Megan.
Can I also confirm the behavior you are seeing when it doesn't work: in a Story Map Tour there is always one tour point currently selected (it's point marker symbol is shown larger on the map than the other points). Are you finding that you can't drag that marker to a new location? Note that Map Tour doesn't let you click on the map to specify the new location for the currently selected tour point: you have to drag that point to a new location to relocate it. It also won't let you drag a different marker to new location: it only lets you drag the currently selected marker to a new location. Does any message appear in the Map Tour Builder when it doesn't work? Also if you open the Console for your browser (i.e in Chrome press F12) do you see any errors listed when this doesn't work?
I don't know what is causing this issue but here are a couple of other things to try. It would be good to eliminate if this is something to do with the particular map you are using in your Map Tour, such as the basemap, the specific spatial extent it is using, or any Organization wide geocoding locators defined in your ArcGIS Online Organization's Admin settings.I t would be good to check on a machine on which you get this issue, do you get the same issue if you create a new Map Tour using a different basemap and extent? And it would be good to check if you get the same issue if you sign in to ArcGIS Online using a Public Account instead of an Organizational account to see that if that eliminates the issue.
- If you are using ArcGIS Enterprise (as opposed to ArcGIS Online) there may be an issue in Story Map Tour in ArcGIS Enterprise versions prior to 10.6.1 where you may not be able to drag points in the Story Map Tour Builder if your map uses a vector basemap that uses a reference layer, such as the Imagery Hybrid basemap or the Light Grey basemap. It would be good if you could try changing the basemap used in your Story Map Tour to see if that fixes the issue.
- Story Map Shortlist has an issue where an invalid locator specified at the Organization level causes entering street addresses in that builder to fail, and we see the same issue via HTTPS if there's an Organization wide geolocator that uses HTTP. It's not quite the same as what you are seeing but that is another thing that signing in with a Public account instead of an Organizational account and making a new tour, would help to eliminate.
Rupert