IB Subscription Contracts Stalled

Categories:
Tags:
Tailored Operational Context
  • Target Database: —
  • Context Type: —
  • Alert Severity: —
  • Triggered Time: —
  • Firing Context: —

IB Subscription Contracts Stalled Alert

Alert ID: ib_sub_contract_stalled Category: Integration Broker Default threshold: 30 minutes

What This Alert Detects

This alert finds Integration Broker subscription contracts that are stuck in New or Working status and have not progressed beyond that state within the configured threshold.

A stalled subscription contract means PeopleSoft received an inbound message from an external system, but has not yet finished processing it. The message is either waiting to be handled (New) or is in the process of being handled but taking too long (Working).

When This Matters

For sub contracts, the most common cause specific to this alert is subscription handler PeopleCode that runs unusually long or waits on an external resource. For broader IB-side causes (dispatcher down, backlog), cross-reference IB Dispatcher Down and IB Operations Stalled.

Severity Logic

ConditionSeverity
Stuck longer than thresholdMinutesWarning
Stuck longer than thresholdMinutes × 2Critical

Alert Details

Each alert item includes:

  • Subscription contract ID
  • Service operation name
  • Current status (New or Working)
  • How long it has been stuck (in minutes)
  • The originating (publishing) node
  • A link to the IB Monitor detail page

Configuration

alerts:
  checks:
    ib_sub_contract_stalled:
      enabled: true
      thresholdMinutes: 30       # Minutes before flagging as Warning
      excludeOperations:         # Operation names to skip
        - BULK_INBOUND_SYNC
SettingDefaultDescription
thresholdMinutes30Minutes a contract must be stuck to trigger a Warning. Critical fires at 2× this value.
excludeOperations[]List of IB operation names to exclude. Use for known long-running handlers.

How to Respond

  1. Click the alert link to go to the IB Monitor entry for the stalled contract
  2. Check whether the IB dispatchers are running on the PeopleSoft application server
  3. Look for a broader backlog. Many New contracts may mean no dispatcher is running
  4. Check application server logs for errors in the subscription handler
  5. For Working contracts, check whether the handler PeopleCode is looping or waiting on an external resource

Relationship to Other IB Alerts

For sub contracts that have already ended in error, see IB Subscription Contract Errors.

For similar stalled alerts on operations and publication contracts: