Hi @Suresh_Rocky ,
I think its maybe because of the bot runs under a different user/context in UiPath Assistant than in Studio, so SharePoint access permissions or authentication are missing.
Since it works from Studio but not from UiPath Assistant, please check the SharePoint permissions and connection for the user running the Assistant. Also add a log before/after the upload activity to see if the upload step is being reached or failing.
UiPath Integration Service connections are created and owned at either a personal level or a shared/tenant level within a folder.
When a process is packaged and triggered via Assistant, the robot executes as a machine-mapped robot account (or unattended service identity), not as you. If the SharePoint connection was created under your personal account and never explicitly shared with that folder/robot, the robot has no visibility into it.
To confirm and fix, go to Orchestrator → Integration Service → Connections and check the connection used by your SharePoint activity. Check its scope, it should show as folder-shared, not tied to an individual user. If it’s personal, recreate or re-share the connection at the folder level so any robot running in that folder can use it.
Also, verify that the version running via Assistant matches what you’re debugging in Studio.
Since the process works correctly when run from UiPath Studio but fails when triggered through UiPath Assistant, please check the execution environment and user account.
Ensure UiPath Assistant is running the process using the expected robot/user account.
Check whether that account has the required permissions to access and upload files to SharePoint.
If you are using a local file path, make sure the file is available to the user/session in which the process runs.
Verify that the same input arguments and configuration are being used when running from Studio and Assistant.
Add logs or use Log Message activities around the SharePoint upload activity to identify whether an error or permission issue occurs.
Also, please share the error message from the Output panel or Orchestrator logs after running from UiPath Assistant. That will help identify the exact cause.