Resubmit Failed Integrations

How to resubmit failed integrations to the Transaction Assistant; Description of the Transaction Assistant.

Integration Hub verifies the validity of data and indicates integration runs that contain errors. Use Transaction Assistant to resubmit integrations that failed because of minor errors.

What is the Transaction Assistant?

Transaction Assistant shows transaction errors in integrations so that, if circumstances are appropriate, you can resubmit the integration as follows:

  • Use Transaction Assistant to resolve transaction errors in the short term when there are only a few data errors, or to meet an immediate deadline when you don't have time to correct the original integrations or data.

    Regardless, you must correct the errors before the next integration run to prevent them from occurring again. Identify and correct the source of the problem in the integration or the data source.

    Example: A punch import fails if the badge number is missing. Use the Transaction Assistant to correct the badge number and submit the failed punch import again. Then correct the badge number in the source integration, or this error will occur again.

  • However in some cases, source corrections are not necessary.

    Example: A person import fails if labor category information has not been entered in the database. Use the Transaction Assistant to submit the failed person imports again after you enter the labor category information. In this case, you do not need to correct the source because the error was caused by missing information, and that missing information is now available.

  • Transaction Assistant cannot resolve integration errors; troubleshoot from Integration Hub and the Integration Designer.

All interactions use APIs. While an API runs, failures can occur as follows:

  • If the syntax in the request is wrong or if the connection fails, Integration Hub shows an error message. The request stops and the failed integration is not reported. You must correct these errors before you can run the request again.
  • If the syntax is correct, Integration Hub creates a record for each item in the request.

    Example: Integration Hub creates a record for each employee in an import of people records, or for each labor category that is imported. The result can be hundreds of records. Integration Hub then validates each record. If any record fails validation, the database is not updated. Instead, Transaction Assistant lists the integration as failed.

Note: You cannot export records of errors from Transaction Assistant to a spreadsheet (Excel) or a PDF file.

Resubmit integrations from the Transaction Assistant

How to resubmit integration runs that had transaction errors from the Transaction Assistant.

  1. Do one of the following:

    • Select Main Menu Maintenance > Integrations.
    • Click Tap Notifications . The number on the button indicates the number of active notifications. In Categories, select Integrations.
  2. Select an integration run.
  3. Check the Run Summary for details.
  4. Click Tap Go to Transaction Assistant.
  5. Check the details in the Transaction Assistant:
    Note: The initial page of the Transaction Assistant can show up to 200 records of errors; scroll to show more records. The Transaction Assistant can load a maximum of 50,000 records.

    Above the table are the following counts of records:

    • Total
    • Selected
    • Displayed: The number of records that have been loaded; scroll to show more.

    The table shows the following:

    • Error Number: The system number of the error
    • Description: A brief error message; hover the cursor over a description to display more information; includes the name of the API tag that has the error. If the same ID has multiple errors, the pop-up shows all of the error messages.
    • Error Date/Time: Date and time of the first error; an error can trigger later errors. The date and time remain the same regardless of the number of times the integration is submitted.

      Example: If a process to import a new person ID fails, all other import processes for that person ID also fail. This can include imports of punches, paycode edits, or schedules.

    • ID: For a failed integration, the specific value varies according to the information that Integration Hub sends to the Transaction Assistant. Examples: person ID, labor category, shift code, or any value that is in the detailed error description. Example: If a failure occurs in a punch import process, ID displays the Person ID for the punch that failed.
      Note: ID does not show the property name, such as person ID, only the value of the property. Hover the cursor over the ID to see the property name.

      If you sort by ID, you sort first by the property that failed, then by the value of that property. Hover the cursor over the ID column to see the name of the property that failed. Example: For a person import process where the Transaction type is People, failures occurred for a number of employees and all failed integrations are sorted together. The integrations are sorted first according to the value of the failed item: Person ID. Then each failure for the employee is sorted.

      Scan the list for related errors. Example: Search all errors that occurred for employee 123456 in the people integration of the person import process.

    • Transaction Type: The import category of the integration. Examples: Data Import, punches, labor categories
    • Transaction Start Date/Time: Date and time when the integration started

      Transaction Start Date/Time is the same as Error Date/Time unless Integration Hub uses the transaction date and time. Example: Transaction Start Date/Time can be the time when the import process starts, and Error Date/Time can be the time of the error.

      The date and time in the Transaction Assistant can be different from the date and time in the import reports. The Transaction Assistant displays Error Date/Time and Transaction Start Date/Time according to the time the errors occurred or the time the integration started. The Import Statistics and Import Errors reports record the date and time when the error information is saved.

    • API Endpoint: The API endpoint that was called and which produced the transactional error.
  6. To see more information about an error, click tap the Description. The slider opens to show detailed information.
  7. (Optional)

    Change the time period. Click Tap Select Timeframe or the arrows or .

  8. (Optional) Filter the list of records as follows:
    1. Click Tap Refine to sort or filter the list of records.
    2. In Refine, select the dropdown for the corresponding column header.
    3. Select or enter the operator and value.

      Example:

      1. Select API Endpoint.
      2. Select Custom to match the text that you enter.
      3. Enter punch.
        Note: This field is for searches for text strings, and regular expressions are not supported.

        Example Refine Filter
    4. Click Tap Apply.
    5. Repeat with more operators and values to filter the records further.

      Example:

      Filter for punch errors for an employee on a specific date as follows:

      1. Select API Endpoint. Select Custom. Enter punch to show only errors that are related to punch integrations.
      2. Select ID. Enter the person ID of an employee.
      3. Select Error Date/Time. Select the date.
  9. (Optional) To download all error records for an integration run to a comma-separated values (CSV) file for troubleshooting, see Transaction Assistant Downloads.
  10. (Optional) To copy the error records to another application, such as a text file or spreadsheet, do the following:
    1. Select an error record, or page down to load all records and click tap Select Max.
    2. Hold Shift while you click tap the last error record that you want to copy.
    3. Press Ctrl+ C.
    4. Paste the records into the other application.
  11. Resubmit an integration as follows:
    • Correct parameters if you can.
      1. Select the Description of the error.
      2. Search for and correct parameters.
      3. Click Tap Resubmit.
    • If the parameters of the integration are correct, but another condition caused it to fail, submit the integration process again without making any changes or edits.

      Example: A business structure import failed because the labor category had not been entered. Once you enter the labor categories, you can submit the business structure import again without making changes to the integration.

      1. Select any field of the error except Description.

        To select multiple errors, press and hold Ctrl while you select errors. You can select up to 200 errors at a time to resubmit or delete.

        To select up to 200 of the errors that are loaded, click tap Select Max . You cannot select more than 200 records, and Select Max selects only the first 200 records in the Transaction Assistant. To filter the error records, click tap Refine.

      2. Click Tap Resubmit.
      3. To resubmit more errors, scroll to load more errors and repeat these steps.
  12. If you see a Warning, select Continue Processing All Selected Transactions in the Event of a Failed Record. Click Tap Yes to confirm.
  13. Click Tap OK to close the confirmation or error message.
  14. Close the panel.
  15. Click Tap Refresh .
    • When you resubmit an integration run, it becomes a new integration and the previous integration run is deleted from the list. If the integration fails again, the Transaction Assistant lists the resubmitted integration run.
    • There is no limit to how often you can submit an integration.

Main Menu — Return to the main menu.

Home — Return to your home page.

Help — Open the relevant help topic in the slider pane on the right of the user interface.

Notifications — The number indicates the number of active notifications.

Time Frame or the arrows or — Change the time period.

Refresh — Update the monitor view.

Select Max — Select up to 200 records at a time.

Delete — Delete the selected records.

Resubmit — Resubmit the selected integration runs.

Refine — Sort or filter the list of records.