Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • TIBCO Cloud? Integration - Connect July 21, 2021 Update Release Notes

    Ana Bahr

    For additional information see:

    TIBCO Cloud Integration Release Notes

    TIBCO Cloud Integration - Connect Known Issues

    TIBCO Scribe Online Connector Release Notes

    New And Noteworthy

    There are no new features in this release.

    Closed Issues

    SCCORE-1463 / SCCORE-4859

    When deleting a large number of flows from an app, there may be a delay updating the user interface causing deleted flows to continue to display. (Case # 01806292, 01890333, 01927480, 01929922, 01941698 01948880)

    SCCORE-6560 / SCCORE-6754

    Deleting apps using the TIBCO Scribe Online API sometimes generates 504 Gateway Time-out errors even though the server is not busy.  With this release, overall time to delete may be increased but succeeds in situations where the load on the server is heavy. (Case # 01942975)

    SCCORE-6685 / SCCORE-6686

    Enabling/Disabling or deleting a large number of flows in an app sometimes causes flows to appear to have been enabled/disabled or deleted but the state stored in the cloud has not been updated. (Case # 01927480, 01944755, 01948890) 

    SCCORE-6693 / SCCORE-6787

    In some cases, when adding a new flow to an existing app, the number indicating the order of execution for the new flow displays as a number that is already in use.  For example, there could be two flows numbered 2 in the list of flows.  (Case # 01949473)


    When an app is running, editing flows, changing the order of flows in an app, locking and unlocking flows, or enabling and disabling flows causes the flows to run out of order. (Case # 01949766)


    Changing the order of flows in an app sometimes generates internal errors and the flows are not displayed in the correct order. (Case # 01942283, 01948880)


    Updating the names of flows in an app and then switching the app to a different Agent sometimes causes the names of the flows to revert to their original names.  ( Case # 01948059)

    User Feedback

    Recommended Comments

    There are no comments to display.

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Create New...