Hi Jennifer! Did you set up this workflow recently? Or has it been working for a while and stopped working recently?
Here are a few things to try (simple to complex). I apologize if any of these come off as too easy, but sometimes it's the little things...
1) Log out of Survey123 and log back in on your mobile device; try the workflow again
2) Delete the downloaded survey in Survey123 and then redownload it in Survey123. Go through the Field Maps workflow to create a new related record
3) Ensure that you have the latest version of Survey123 installed on your mobile device; it can be updated through the Apple or Google Play stores
4) Ensure that you're using the latest version of Survey123 Connect to build/publish your survey; the latest version is 3.13. If you need a newer version, download and install it. This won't impact your existing surveys. Republish the survey. Update the survey on your mobile device before trying the workflow again.
5) Uninstall and reinstall Survey123 on your mobile device. Be sure to submit any surveys in your outbox on your device first, they'll be deleted when you delete the app!
6) Double check the URL you built in Survey123. Make sure it has the right structure as shown at 11:26 in the video:
arcgis-survey123://?itemID=[Item ID]&field:ParentGUID={GlobalID}
Specifically, what item ID did you use? It should be the item ID of the Survey123 survey item in ArcGIS Online. Sometimes people will use the item ID of the hosted feature layer; this is incorrect.
Give these a try!
I wanted to touch on why submitting a survey directly with Survey123 doesn't link your submissions to features. Remember that this workflow is powered by the GlobalID value being copied from the parent feature to the ParentGUID field of the related record. This is how inspection records are paired with the correct parent feature. Specifically, the last part of the URL in the web map (&field:ParentGUID={GlobalID}) tells GIS "Hey! When you open the survey, copy the GlobalID value from this feature I clicked on and paste it into the survey's ParentGUID field." As a result, the GlobalID and ParentGUID values are linked when you use Survey123. If, however, you open the survey using ONLY Survey123, no GlobalID value is copied from a parent feature and pasted into the related table. As a result, the new inspection you submit has a blank ParentGUID field value and is not linked to any parent feature. It's considered an "orphan." It sits in the related table but isn't actually related to anything in the parent layer. In short, you need the ParentGUID field to be populated and the URL does this for you in the Field Maps/Survey123 workflow. Survey123 submissions will still be stored in the table, but they won't be related to a parent feature.