Ensure the WAAE Client Utilities are installed on the iDash server and configured for the instance to which iDash is connecting.
In the iDash Admin Tool, check the environment settings for the AutoSys server that is configured...
Ensure these variables are set to the proper location for the WAAE Client installed on the iDash server. For Windows servers, the library path variable would be blank. However, if the iDash server is UNIX/LINUX, the library path field should contain the path to the WAAE Client lib directory. (typically the same as AUTOSYS with /lib on the end).
Test the utilities outside of iDash and make sure you are not getting any errors. For example, run an 'autorep -J <job_name> -q' and make sure it provides the jil for the specified job. If that gets any errors from the command line, iDash will be getting the same error behind the scenes and will post the "Artifact not found" error as a result.
NOTE: The WAAE Client Utilities are 32-bit. If your iDash server is UNIX/Linux, the client requires the 32-bit version of certain O/S packages. Please consult the following link for specific O/S package requirements.