Skip to main content

Troubleshooting Remote Tasks

anaddell
Updated

You can troubleshoot the following issues with remote tasks before contacting technical support:

Missing jobs from job export

  1. Review the export file to ensure that the job is not included in the export file.
    1. Open the export file from the Attachments tab and search for the job within the file.
  2. Ensure that the missing job has met all criteria for inclusion in the export.
    1. If there is a specifications document for the export, review the criteria to ensure that the missing job meets the requirements.
    2. Review the Export Profile and settings and ensure that the missing job meets these requirements.
    3. Review the log file and check if the job is referred to as “skipped” in the export. For example, if a line indicates that the job is skipped due to filters will be like: 7/16/2018 1:55:49 PM|Info|Record #5 skipped due to filter expression (001NHGeneral Clerk III).
    4. If only changed jobs are included in the export (since prior export), ensure that the user has updated the job through a “Form Editor screen” or “Job Description Name Change” screen. The saved form edits and job description name changes are the only edits that will trigger the Date Last Changed field that is used in exports to identify changed jobs.
  3. If the job is not in the export file even after the necessary criteria, contact our technical support team.

Job details are not as expected with job export

  1. Review the export file to ensure that the job was included.
    1. Open the export file from the Attachments tab and search the job. If the job is not included, refer to the previous section, “Jobs are Missing from a Job Export issue.”
  2. Review the job in JDX. The export should contain the current values saved in the job. If a value is displayed in the job which is not in the export file, check the following:
    1. Ensure that the correct field is exported.
    2. Find the name of the field expected to export by reviewing the master template.
    3. Find the name of the field that is actually exported by reviewing the export profile. The export profiles are identified in the remote task. Open the profile in Job Description Export and verify which field is exported. The data binding string of the export profile should match the binding property in the master template.
    4. Contact our technical support team, if you require assistance in updating the Export Profile.
    5. In some cases, choice lists will send display value vs. value, review specifications, and the master template's choice lists for the export as needed.
  3. Check if the job is in the workflow. If the job is in workflow, it may be that the last saved fields (prior to workflow) are included in the export and not the current fields (workflow changed fields). Contact our technical support team if a change is required such that workflow changes are included in exports for jobs undergoing workflow, rather than values saved to a job prior to workflow.
  4. Check the specifications document for the export, to ensure that the fields included in the export are as expected.
  5. Check the data in the export file for accuracy. If fields in the export file do not match the job (and you have already reviewed specifications, workflow status, master template, and Export Profile), contact our technical support team.

Employees or jobs are not updated via employee or job import

  1. Review the import file to ensure that the employee is included in the import file.
    1. Open the import file from the Attachments tab and search for the employee within the file.
  2. Review the log file for any messages regarding the record in question.
  3. Review the field mappings.
    1. Download the import file.
    2. Identify the import profile.
    3. Goto Job Description Management –> Import.
    4. Select either Import Job Description Data from Excel or Import Employees, depending on the type of import.
    5. Walk through the wizard, using the file downloaded from the remote task output.
    6. Review the field mappings to see the columns in the import file and where they are mapped to in JDX.
    7. Modify mappings if necessary.
  4. Contact our technical support team for any assistance.

Remote task fails

  1. Open the Remote Tasks.
    1. A failed task error is displayed in the Last Result column. Review the log for confirmation (there should be an error appearing in red).
  2. Run the task again and check if it succeeds.
    1. Note the results of the task.
    2. If there is no error, the issue may already have resolved.
    3. If the error persists, contact our technical support team.

File integration issues

File export integration issues

1. Check the system data in Show Tasks Output & Logs.

2. Check the transferred file (via FTP).

File import integration issues

1. Check the FTP file.

2. Check the system data.

Remote tasks and their installation folders are available on AppSever1 (169.53.20.188). Please contact Mike Miller (Director of SaaS) if you don’t have the access to the server.

Remote Task Imports

Employee data in JDXpert doesn’t get updated properly from the HRIS system or keeps reverting to the old values

1. Check that the file was correctly uploaded on the FTP.

a. Confirm the date and time (last updated) matches with the uploaded file.
b. Confirm the file name and file extension are correct.

2. Check the remote task on the AppServer.

a. Confirm the task ran on time and began after the file was uploaded on the FTP server.

b. Check the Logs folder (in each client’s bin) to see additional details.

c. Confirm the data is correct in Tasks Output and Logs.

d. Download files from the Attachments tab for the last remote task occurrence and check that the data is correct.

  • If incorrect, confirm the input and output directories of the FTP.
  • Confirm that the remote task’s step configuration is using the correct import profile.

3. Check the import profile

a. Check the import profile configurations – layouts, delimiters, and/or file conversion.

b. Run a preview of the expected file with the assigned import profile in a test environment to confirm results

Remote Task Exports

ATS data is not transferred correctly through JDXpert file transfer

1. Check the job data in Notepad (not Excel) to see the raw data.

2. Check the export profile:

a. Check the manual export in the Job Management tab.

b. Check the export profile configuration (column settings/data tokens).

3. Check the remote task on the AppServer.

a. Confirm the task ran on schedule and has completed prior to the transfer schedule from the ATS.

b. Confirm the data is correct in Tasks Output and Logs

c. Download files from the Attachments tab for the latest remote task occurrence and confirm the data is correct.

d. If incorrect, confirm that the remote tasks step configuration is exporting using the correct export profile.

e. If correct, confirm the input and output directories of FTP.

The output directory should match with the directory (as for the file drop that the ATS task is picking up from). The file name should be exactly what the ATS system is expecting.

4. Check the data on the FTP.

a. Confirm that the file transferred on the FTP is correct and contains the correct data.

 

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk