This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
My guess is that you need to manage your workflow dependencies.
Managing your Workflow Dependencies is a best practice for sharing because of the frequency that path references become broken when sending workflows between analysts, sharing on the Gallery, or scheduling workflows. The reason for this is that most path references are done specific to the system that a workflow was created on, before the workflow is moved to another location.
Try to change your output path to UNC
Found in the Options > Advanced Options > Workflow Dependencies
I believe it's because that file is being packaged as an asset file when publishing to your Gallery. You can define which assets should and shouldn't get package when you're saving out to Gallery as illustrated below.
That said, you'll need to ensure that the location of your file is at a location that the servers run-as account has access to. If the file resides on a network share, as @VianneyM had mentioned, you'll need to be sure that the UNC path (\\fileserve\mydepartment\something\myfile.xlsx) is used and not a mapped letter.