Feb 11 2018 11:59 PM - edited Feb 12 2018 12:00 AM
Hi,
I'm experimenting with Azure Function, Logic apps/Flow to replace an existing SharePoint Workflow.
I've found a weird issue where the client context get mixed up when multiple flows are running in parallel and try to call the azure function. I've found a workaround to overcome this issue by allowing only one job on the azure function environment. It's not a good solution, therefor I want to find the root cause of the following error message :
Exception calling "Load" with "1" argument(s): "The object is used in the context different from the one associated with the object."
Has someone encounter a similar issue?
Cheers
Bernd
Aug 27 2023 10:53 PM
Jan 18 2024 09:38 AM - edited Jan 18 2024 09:39 AM
I'm still having the same issue...
My use case is with getting properties of a SharePoint Online item that was just created with Copy-PnPFile