I've created a custom geoprocessing tool from a Python script that uses feature layers hosted on our Portal as inputs. The tool runs without issue when the local version is used, but when I publish the tool to Portal and try to use the hosted version in Pro or Portal it says it can't access the feature layer.
The feature layer is shared with our organization and the tool is currently private, but the account I'm using in Pro and Portal owns both. The layers and Portal both use HTTPS.
Has anyone ever come across this issue before? I'm at a loss on where to begin to troubleshoot it. I don't think the issue is with the script itself because it runs fine with the exact same inputs before the tool is published.