You're right. I'm looking to link the document that triggered the workflow to start with the document that is found with the search repository task.  Using your recommendations, it shows the error message of, "The starting entry could not be found."

I've tried to adjusting my forms process a bit as well, having the workflow be triggered before and after this document is saved to the Repository.  (The file I'm linking to what is found by the search)

Edit: both configurations of the form process produce the same error.  The only difference is the one way has the error show before the search result, like the attached screenshot, and the other way has the error show after the search result.

I have to be missing something with your Forms process that I might not be able to help you with.  

When I start the Business Process below on a selected entry in the LF client the end result of the workflow is a set of linked document (as one would expect).

Essentially, the idea is that when a person fills out a form to cancel the automatic payment authorization, Laserfiche is meant to find the original setup agreement, and link the setup with the cancellation form.  When cancellation is chosen in the starting form, it follows the path found in the screenshot.

I get the same result of "The Starting entry could not be found" if I have the workflow and repository in the locations in the screenshot, or if their spots are reversed.

I wouldn't be surprised if there is a better method to involve workflow.  Combining workflow and forms is something we are trying to do more of.

I can see your logic but I am not sure if a business process is the way to go? 

When the new form cancellation document is created in Laserfiche I assume there is some metadata assigned?  What metadata are you using to search for the original Authorization document and is there a metadata field to indicate that the new document is a cancellation?

Yes.  We have a custom of data field that has been used on other forms.  Its simply titled Transfer Type.  There is a question on the form asking the type of transfer, either new set up or cancellation, and it displays the info needed on a cancellation using field rules.  The user then fills out a little bit of info and has the customer sign to verify they are cancelling the transfer.

Using this info, I'm able to lookup and find the original new transfer agreement.  (That's the search repository step in workflow).  By using some info such as account number, date, type of transfer, and share ID, I'm able to filter it down to 1 result consistently every time.