I am unable to debug locally on my machine using Studio Web. The process halts at the trigger during the initial action. This is the exception returned to me:
2026-01-30 15:01:44.915 GMT−3: Error: System.AggregateException: One or more errors occurred. (Solo se puede tener acceso a un ActivityContext en el ámbito de la función en la que se pasó.
Object name: ‘System.Activities.AsyncCodeActivityContext’.)
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Wait()
at UiPath.Core.Activities.Orchestrator.OrchestratorService.GetOrchestratorVersion(ActivityContext ctx)
at UiPath.Core.Activities.GetCurrentJobInfo.ExecuteAsync(AsyncCodeActivityContext context, CancellationToken cancellationToken)
at UiPath.Shared.Activities.AsyncTaskCodeActivityImplementation.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at UiPath.Shared.Activities.AsyncTaskCodeActivity.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
System.ObjectDisposedException: Solo se puede tener acceso a un ActivityContext en el ámbito de la función en la que se pasó.
Object name: ‘System.Activities.AsyncCodeActivityContext’.
at System.Activities.ActivityContext.ThrowIfDisposed()
at System.Activities.ActivityContext.GetExtensionT
at UiPath.Core.Activities.ActivityContextExtensions.GetWorkflowRuntime(ActivityContext context)
at UiPath.Core.Activities.ActivityContextExtensions.GetOrchestratorSettings(ActivityContext context)
at UiPath.Core.Activities.Orchestrator.OrchestratorService.<>c__DisplayClass8_0.b__0()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
— End of stack trace from previous location —
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
Studio Web does not support local debugging for workflows that depend on Orchestrator context (Triggers, Job Info, Assets, Queues).
The ObjectDisposedException occurs because no Orchestrator Job exists during local execution.
Try this solution Publish the process and run/debug it via Orchestrator. Local debugging is not supported for such workflows.
If it’s helpful please mark as solution and let me know if you face any issue
Thanks
Local debugging does not provide a full Orchestrator job context, so triggers and activities like Get Current Job Info fail with AsyncCodeActivityContext/ObjectDisposedException.
You can Test triggers by publishing and running the job from Orchestrator, or debug without triggers locally.
Studio Web can’t fully debug trigger-based or Orchestrator-dependent workflows locally. Activities like Get Current Job Info need Orchestrator context, which isn’t available in local debug, so it fails at the trigger. Publish and test from Orchestrator, or temporarily remove the trigger to test the logic locally.
“However, Studio Web does not allow me to remove the triggers; it insists on starting with one. How can I debug this workflow? The strange thing is that I am certain I managed to do this several months ago, but now it doesn’t work. Did something change? Did I accidentally delete something? It is a workflow that I used and debugged from Studio Web.”
@Matias_Clemente.Arg
Studio Web always requires a trigger and does not allow removing it.
What changed is that local debugging for trigger-based workflows that rely on Orchestrator context is no longer supported.
The error occurs because no Orchestrator Job exists during local execution.
To debug this workflow, it must be published and run from Orchestrator. You didn’t delete or break anything.
If solution helps you please mark as solution
Thanks