@Hugo_Casqueiro I’m not seeing UiPath.Workflow.Runtime referenced anywhere? It looks like you used the Activity Creator VS Extension? V4.0 I’m assuming? Is there a reason you’ve heavily modified the async timeout structure provided by the activity creator? Also looks like you must’ve made the SubmitDocumentResponse required but changed your mind and updated that in the CacheMetadata section?
It might be worth starting from a clean slate using Activity Creator newest version (if not already) don’t modify any structure in the project other than the references to packages that aren’t supported. (e.g. the too new version of UiPath.Workflow.Runtime, not sure if you need to modify any others, only perform one modification each time and republish your packages in debug mode so that you get new version numbers, package your project into nuget simply by right clicking on the design project and publishing from there.)
Side note: just to keep things simple for a first attempt, maybe don’t use the timeout functionality and just try a simple activity with no timeout
Thanks @Aeryn_Connerley I’ve done a new project again from scratch, based on Activity Creator, and it seems fine. I think the last problems was raised after updating nuget references, as VS suggests. So, no references updates.
I honestly gave up for awhile on this as I had other priorities on my plate and UiPath has not been forthcoming with a clear response to the question proposed. I haven’t tried the update in the past written by Khachik Gejagezyan. Either way, the burden should fall upon UiPath to provide better, clearer documentation.