This lesson provides troubleshooting tips for issues with GURU. There are several types of Zaps: Zap that sends data to a vendor (export Zap), Zap that runs the Profile that is an import of data from a third party vendor (import Zap), or a Zap that runs a rule that is internal to the system.
Before You Begin
The troubleshooting steps below will assist in identifying and resolving common errors when working on GURU exports and imports.
ZAP errors out, client reports an error:
- Go to Zaps.
- Select Action next to the desired Zap.
- Choose History from the menu. The History then will present the issue that occurred.
Zap Errors Out
Please navigate to the ZAP right click on the down arrow icon and then look at the History (see image in the Export Zap section). The History then will present the issue that occurred there.
Please note that at this point in time, the ZAP success/failure does not automatically mean it is either working or not working. The ZAP just runs the profile for importing data and the ZAP is just a conduit for the connectivity of getting the file from the SFTP server to the Profile.
- Check the error message on the ZAP. See if the error message says “File not found” error. The third-party vendor uploads the file that needs to be imported into the SFTP (whether or not it is provided by eSD) at a certain time each day. The ZAP (based on the timer) reaches out to the SFTP grabs the file and sends it to the Profile to process it. Once the processing is finished, the file itself is deleted from the SFTP. After the one-time processing is completed, if you keep clicking the Run – the process is going to fail because the file is no longer there and it can ONLY be run after the file is re-uploaded by the third party vendor.
- If the Zap fails with another reason other than “File not found’ – see if there is a connectivity issue as mentioned above.
These issues must be resolved by the organization. The eSD Support team cannot resolve the above issues.
Zap does not error, but data is not being uploaded into eSD
- Check the ZAP and look for the connecting profile – it will be listed under Profiles. Navigate to that Profile to look at the history of the import, export the error logs and see if the student in question and the data is present in the file and there are no errors. If the student is not present in the file, then it is a third-party vendor error. If the student is present in the file and an error message is provided, then it is a third-party/data entry error on the vendor system. Please reach out to the vendor to correct this issue.
- If all the above are correct and the profile says data imported and still the student/information does not appear in eSchoolData, please contact eSD support.
SFTP provided by eSD
Log into the SFTP. If you do not have your please contact support. Verify the file is on the SFTP. If the file is there but not being imported:
- If the third-party vendor hosted locally on the district server, but no import is occurring, there would be an additional process that was setup on the local server to download the file from eSD SFTP to send it to a local folder (case in example Nutrikids which could not pick up data from an SFTP and can only do so locally), in which case the administrator should check the Scheduled Task. It may need a password update.
- The end-user network administrator confirms that the file is reaching the local folder but still import does not occur. Please reach out to the vendor to correct this issue.
- The file is not reaching the eSD provided SFTP and is generating an error. Please contact eSD support.
SFTP provided by third-party vendor
- File is not reaching the third-party provided SFTP. Check if permission is denied or other such unspecified error occurred. Login using Filezilla or CoreFTP to confirm that you can actually login to the third-party vendor provided SFTP. If you cannot login to the SFTP, please reach out to the vendor to correct this issue.
- File is reaching the SFTP when logging in using the downloaded CoreFTP or Filezilla but receiving an error message on ZAP. Re-enter credentials on the Servers Configuration > Servers area.
- File is reaching the SFTP when logging in using the downloaded CoreFTP or Filezilla but receiving an error message on ZAP and even after re-entering the credentials then check Configuration > Storage area to see if the folder name is properly setup.
- All the above settings are correct and previous history seems to have worked and a release has occurred at eSD level. Please contact eSD support.
Zap that Runs a Rule
This is a trigger to run the rule setup in the ZAP. If something is not updating properly go to the actual Rule that the ZAP is set to be running on a certain time, run the Simulation on the rule manually and see if there are errors being generated. If there are errors, please contact eSD support.