Long Running Interrogation Window Start/End Time Not Reflecting Set Interrogation Window Duration (Doc ID 2556692.1)

Last updated on JANUARY 20, 2020

Applies to:

Symptoms

On : 2.2.0.2.0 version, Environment

ACTUAL BEHAVIOR
---------------
Long Running Interrogation Window Start/End Time not reflecting set Interrogation Window Duration

We have been testing Interrogations in MDM 2.2.0.2 and have set a 15 minute interrogation window duration. However, when the outbound interrogation is created and sent, the Interrogation Window Start/End times are in the range of 2-2.5 months long.


EXPECTED BEHAVIOR
-----------------------
It is expected that these parameters would create a 15 minute long span between Interrogation Start and Interrogation Stop.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create activity for Scheduled Read
2. Set 15 minute interrogation window.
3. Save and transition the Activity such that the outbound message is sent out
4. Notice the Interrogation Window End Date/Time is way too far in the future.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use these scheduled read activities because they would be open with the head end for too long before being returned to MDM.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.