Why does invoke workflow fail after renaming folders or refactoring XAML files, even though paths look correct?
Thanks A Lot !
Hi @Aarya_singh
Remove and re-add the invoke workflow file activity using browse
Ensure the invoked XAML is included in the project.json
Republish the process after refactoring
Bienvenida 
1 Like
Invoke Workflow does not rely only on the displayed path; it keeps an internal reference to the XAML. Renaming or moving files breaks that reference silently. Re-adding the Invoke Workflow or re-browsing the XAML forces Studio to rebuild the reference, which fixes the failure.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.