The remote process took longer than the allowed time to complete and was aborted.
Most likely the time allotted to complete the process is too short. Depending on the operation being performed, it could be that the operation has locked up or it may represent a bug. If this occurs during a deployment with PDQ Deploy then it can be that the application being deployed is not being run silently, i.e. it's waiting for user input which will never come.
If deploying an application with PDQ Deploy, ensure that the proper silent parameters have been entered.
If those are correct, Raise the timeout in Preferences for the operation (Scanning for Inventory or Deployments for Deploy) to allow more time for the task to complete.
To change that setting globally, go to Options > Preferences > Deployments > Timeout.
This can also be set at a package level for packages that just like to take their time.
In the deployment package window, go to Properties > Options > Timeout > Use Custom Timeout.
If the problem persists, there may be an issue with the remote process which may entail sub additional troubleshooting, in which case contact firstname.lastname@example.org.