If your job fails with a Status 404 or Not Found it means the resource is somehow missing in the partner's app. This may happen if:
You removed resources in the external service.
Cancelled your account in the external service.
The service improperly returns a 404 instead of a 200 status code with a blank body.
Solution: Double check that your data is not empty in your external app. Then re-authorize and restart the job.