Why did the GET job not find a Sphere export file?

The GET process may fail to find a file on the Sphere side to FTP to Team Approach (TA). A warning email like this would be received:
This is a message from sphere_sync_get_v2.1.sh.
The file sp-to-ta.MM_YYYY_DD.HH.MM.SS.zip did not exist in <filepath> 
at the time of this script running on the Kintera FTP website.  
No file has been placed in <filepath>.
The the name and locations of log file created for this script is <filepath>
There are three potential causes of this issue:
  1. A file was not sent to Sphere from TA. The Sphere export is triggered after receiving an import file from TA. Check that a file was produced and successfully transferred to Sphere.
  2. The PUT process to send the file to Sphere was delayed, so the export is not finished when the GET process runs to get the next file. Rerunning the GET later in the day should get the file.
  3. If neither of the above are the case, it is likely that the Sphere export failed due to a timeout after too many records were updated on the Sphere side. Contact Support for assistance.

Environment

 RSR

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.