Omni Exporter events

Integrations > Data Export > Omni Exporter > Events

The Events screen tracks and reports on each Omni Exporter export event. The list includes all events that have not been purged from the system as specified by the OE Events Retention Schedule option on the Company settings screen.

Use this screen to:

  • Confirm an export was delivered to the target system, and to get information about the state of that export.

  • Examine the exported data included in the event.

  • Examine the request headers sent to the target system.

  • Examine the response headers sent from the target system.

  • Debug Omni Exporter problems.

Using the Events screen

After an export event happens, it is listed on the left side of this screen, with the most recent at the top and the oldest at the bottom of the list (up to 10 days), up to 10,000 events.

  • Select an event to see the processing results.
  • Filter the results by selecting the Omni Exporter that processed the event.
  • The events are color-coded to provide a quick status
    • Black — The event was processed successfully.
    • Purple — There was a processing error, or a retry is pending.
    • Gray — Omni Exporter or Auto Importer was run in pretend mode (either Pretend or Active with pretend processing mode).
List of events showing Black for successful, Purple for error, and Grey for pretend mode

The right side of the screen lists the properties and provides links to more detailed information.

Properties

Properties summarize the event.

Event activities

List of the export activities that happened while processing this event, with the first (oldest) activity at the top. The list includes this information for each activity:

  • Date — Timestamp of the event activity.

  • Status — Status and description of the event activity, including:

    • Created — The event started. Description states how many records will be exported in the event.

    • Queued — Event is ready for export.

    • Running — Exported is running.

    • Success — Target system accepted the request. Description states the response status, and the size of the response, if any.

    • Failed — Target system rejected request, was not available, or did not send a response within 120 seconds. Description states the reason for the failure; except when the 120 limit was exceeded, then there is no description.

    • Retry — The exporter will retry to connect. Description summarizes the retry number and when the retry will re-queue the event for processing.

    • Force retry — A retry was manually triggered with the Retry event button on this page.

    • No retry — Export failed and no more retries will be attempted. The 

  • Description — Detailed description of what happened, including success and failure summaries.

  • Details — Links to reports describing the activity. Use this information for debugging issues. Some reports include:
    • Request — The (Omni Exporter) Request header sent to the target. Happens when Status is Success.
    • Response — The (target system) Response header returned to Medallia. Happens when Status is Success.
    • Result — The content passed to Auto Importer from the specification's HTTP Response Processing.
    • Processing report — The Auto Importer processing report. See Feed Files for details about this report.
    • Login Request — The (Omni Exporter) OAuth Login Request header sent to the target. Happens when Status is Success. This happens whenever the system needs to reauthorize an OAuth login on the target, and the frequency depends on the configuration of the target system.
    • Login Response — The (target system) OAuth Login Response header returned to Medallia. Happens when Status is Success. Same note as Login Request, above.
    • Stacktrace — A significant error happened, such as due to an error in the JavaScript included in the Omni Exporter specification. This should only appear when the Status is Failed.
Exporter
The Omni Exporter that processed the event.
Kind
Status if the Omni Exporter specification, one of Active, Pretend, or Active with Pretend.
Event data

The data fields and values sent to the target system. The fields are the ones selected in the Omni Exporter specifications' Field used in the action property, and the format is always:

{
  "changedEntities":[{
     ... data fields and their values as name/value pairs ... 
  }]
}
Action
Summary of the HTTP Request Assembly defined in the Omni Exporter specification.
Response handler
The Auto Importer specification that handled the response, if any. Otherwise reports None.
Retry policy
Summary of the Omni Export specifications Retry Policy.
Retry event
Manually force a retry. The is typically done when the Status is Failed or No Retry (to try again), or Retry (to retry sooner than the wait period).
Tip: When there are many failures that need to be retried, such as due to a network connectivity issue, consider using the Event bulk retry screen instead.