TIBCO incident

Integration - Connect - AWS (US) - Performance Degradation

Minor Resolved View vendor source →

TIBCO experienced a minor incident on June 23, 2022 affecting Scribe® Agents and Scribe® API and 1 more component, lasting 9h 2m. The incident has been resolved; the full update timeline is below.

Started
Jun 23, 2022, 10:15 PM UTC
Resolved
Jun 24, 2022, 07:18 AM UTC
Duration
9h 2m
Detected by Pingoru
Jun 23, 2022, 10:15 PM UTC

Affected components

Scribe® AgentsScribe® APIScribe® Solutions

Update timeline

  1. investigating Jun 23, 2022, 10:15 PM UTC

    Please be advised that Integration - Connect is experiencing an issue with agents API. The TIBCO team is investigating this issue as a priority. While this is occurring, customers may see that agents are in Heartbeat Failed/Late state, and Flow debug might timeout or take longer, Connection creation/test times out. Scheduled and event-based Connect Apps will continue to run with some exceptions, and you will see a delay on Execution History updates.

  2. investigating Jun 23, 2022, 11:16 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 24, 2022, 12:19 AM UTC

    The issue has been identified and is being addressed. We are actively monitoring all parts of the system.

  4. monitoring Jun 24, 2022, 02:31 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Jun 24, 2022, 05:22 AM UTC

    We are continuing to monitor for any further issues.

  6. investigating Jun 24, 2022, 05:25 AM UTC

    We are seeing some issues with Scribe API in combination with Agent slowness. We are looking into it on priority. While this is occurring, customers may not be able to login to Scribe or see the Apps/Solutions, they might see that agents are in Heartbeat Failed/Late state, and Flow debug might timeout or take longer, Connection creation/test times out. Scheduled and event-based Connect Apps will continue to run with some exceptions, and you will see a delay on Execution History updates.

  7. monitoring Jun 24, 2022, 06:55 AM UTC

    A fix has been implemented and we are monitoring the results.

  8. resolved Jun 24, 2022, 07:18 AM UTC

    This incident has been resolved.