X

The Integration blog covers the latest in product updates, best practices, customer stories, and more.

  • November 10, 2020

Track scheduled instances from submission

Arya Sanyal
Software Development Director

"Just clicked on Submit Now action, and when I navigate to Tracking there's no instance! Kind of lost, I click Refresh multiple times to know whether my integration actually triggered."

Or

"Started a schedule, but on Tracking there's nothing to indicate I have started something until the instance actually starts executing!"

Sounds familiar? We have an enhancement to help you with a more streamlined monitoring experience for scheduled integrations.

Synopsis:

As soon as you trigger a Submit Now or start a schedule, an integration instance gets created immediately. This also shows up on Tracking and confirms not only the fact that your action is successful but also allows you to track the execution no sooner than you submit.

Pre-requisite:

You should be on Oracle Integration Cloud version 20.37960 or later.

Details:

  1. Till now when you triggered a Submit Now, a banner slid up with a confirmation message that included the Request ID of the submission. This changes now. With this enhancement, the message will now include the Instance ID. Clicking on it will directly take you to the Tracking page and display the triggered instance.
  2. On the Tracking page, the triggered instance no longer shows the Request ID. It is not required for tracking the scheduled instance anymore. However, you can still directly navigate to the Schedule Overview page from the Tracking page using the menu which appears on hovering over an instance.
  3. Clicking on the Eye icon launches the Activity Stream. And you can observe some interesting new data there.
    1. Schedule request submitted: 
      • This denotes the point at which the request to trigger the scheduled integration was submitted
    2. Schedule request started running: 
      • This shows the time when the submitted request started executing
    3. Schedule paused: 
      • This shows the time when a scheduled was paused
    4. Schedule resumed: 
      • Similarly, this indicates the time when the schedule was resumed (from paused state)
  4. You will also notice that two new states have been introduced for an instance.
    1. Waiting:
      • This shows the scheduled integration instance is waiting to execute. Typically this is the state of an instance when it is scheduled to execute sometime in future
    2. Paused: 
      • This indicates the schedule has been paused, so the instance is also paused.
  5. In both the above instance states (Waiting and Paused), users can choose to Abort the instance using the Abort button that shows up on the row on hover
  6. There is also a new menu option ("Schedule") which allows you to directly navigate to the Future Runs page for the integration. Clicking "Back" button on the Future Runs page brings you back to Tracking.

 

What happens when you abort an instance in Tracking?

Suppose you have defined a schedule to execute every 24 hours (daily 9:00AM) starting tomorrow (Tuesday). As soon as you start the schedule, an instance gets created and moves to Waiting state. It will trigger the integration on Tuesday at 9:00AM as scheduled. Till then it remains in Waiting state.

For some reason you want to abort the schedule as you do not want it to execute on Tuesday. Using the new Abort button, you can accomplish this.

Aborting the instance will move the instance state to Aborted, and it will reflect on the Activity Stream as such. Also immediately, another instance gets created which again moves to Waiting state. Don't get confused by this. This is the instance for the next day (Wednesday) which is now created and is waiting to execute.

To explain this new behavior, in the below figure InstanceId 10000015 was aborted. As soon as you refresh the page, you will find the state shows Aborted; and a new InstanceId 10400001 gets created. And this instance is in Waiting state. This new instance is for the next run that gets submitted automatically on aborting the previous instance.

Please note: The same behavior will also be observed when you do not abort the instance and allow it to run. It starts running at 9:00AM Tuesday and soon the next day's instance also gets created and moves to Waiting state.

 

Here are the main highlights of this change in behavior:

  1. Executing Submit Now shows instanceId instead of requestId
    • Previous behavior
    • New behavior

      •  
  2. Clicking on the banner link immediately shows the instanceId in Tracking
    • Previous behavior
    • New behavior
  3. Activity Stream shows new milestones
    • Previous behavior
    • New behavior
  4. Pausing a schedule shows the instance as Paused
    • Previous behavior
      • There was no change observed in Tracking as the instance waiting to execute was never displayed
    • New behavior
  5. Resuming the schedule moves the instance back to Waiting state (waiting for execution)
    • Previous behavior
      • There was no change observed in Tracking as the instance waiting to execute was never displayed
    • New behavior
  6. Scheduled instance in Waiting or Paused states can be Aborted in Tracking
    • Previous behavior
      • Runs could only be aborted from Future Runs
    • New behavior
  7. New menu item to navigate to Future Runs
    • Previous behavior
      • You had to click on "Request Id" link to go to Future Runs page
    • New behavior
      • New Schedule menu item to navigate to Future Runs page

Join the discussion

Comments ( 2 )
  • Dheeraj Tuesday, November 17, 2020
    Duration on job completion shows time difference between when schedule request was submitted and when job got completed.

    This is not true duration of job run.
  • Arya Sanyal Tuesday, November 17, 2020
    Thanks for your feedback, Dheeraj. We will look into this.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.