Jump to content
  • TIBCO Cloud? Integration - Connect March 2022 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.

    Migration And Compatibility

    SCCORE-5261 / SCCORE-5985

    IMPORTANT NOTE: We are updating the  TIBCO Cloud Integration - Connect Agents to leverage a new SQL LocalDB database in this release. Agents are automatically updated and no action is required on your part. The upgrade process may take a long time depending on the amount of data in the current Agent Database. Best practice is to allow the process to run undisturbed.  You can check the size of the Agent database by navigating to the Agent installation folder. The default installation location is:  C:\Program Files (x86)\Scribe Software\TIBCO Scribe® Online Agent\Scribe.sdf  The maximum size is 4 GB.  (Case # 01934242)

    Changes In Functionality


    Third-party TIBCO Scribe Online Connector developers should note that the list of .dlls installed on an agent is changing with this release. For the updated list, see TIBCO Scribe Online Connector Certification & Release on the TIBCO Support site. https://support.tibco.com/s/article/Uploading-Your-Connector


    The backlog of queued messages for a Request/Reply flow is limited to 100 messages. When the queue contains 100 or more unprocessed messages, the system generates errors with HTTP Status Code 429 and does not accept any more messages in the queue. When enough queued messages have been processed, new messages are accepted again. 


    TIBCO Cloud? Integration - Connect throttles the number of inbound messages processed by the agents to 20 messages per batch for both the Connect cloud agent and the Connect on-premise agent. When the batch is complete, the agent requests another batch of messages until the Message Queue is empty.


    If the Flow designer is left idle for more than 30 minutes, any changes to the flow are saved automatically and you are logged out of the system. The revision of the flow that is auto-saved is marked in the Revisions dialog with the comment: Flow auto-saved due to an inactivity logout. The last revision of the flow with this comment represents the latest auto-saved flow. The next time you open that flow, a message displays to alert you that it was saved automatically. 


    If scheduled maintenance is in progress and the software being deployed involves changes to the Agent, Agent installations are temporarily disabled and a message similar to the following is displayed: 

    Agent installs are disabled temporarily. Check the TIBCO Cloud Services status page for more information.

    Once maintenance is complete, you can install Agents as needed. 

    SCCORE-5263 / SCCORE-7135


    Flows now support a maximum of 250 Blocks. If you have a flow that contains more than 250 Blocks it will continue to run. If you open a flow that contains more than 250 Blocks you cannot save any changes made to the flow until you reduce the number of Blocks. Best practice is to create several smaller flows that run in sequence within an app. 

    TIBCO Cloud Integration - Connect API


    Cloning large apps using the API sometimes generated HTTP Status Code 504 Gateway Time-out errors even though the server was not busy. (Case # 01942975, 02035644) 

    To address this issue we have added a new API method that clones apps asynchronously. The clone is created in a thread and, using a second method, the status of the clone command can be polled. 

    POST ?/v1?/orgs?/{orgId}?/solutions?/{solutionId}?/cloneAsync

    GET ?/v1?/orgs?/{orgId}?/solutions?/{solutionId}?/cloneAsync?/{cloneId}

    The existing POST ?/v1?/orgs?/{orgId}?/solutions?/{solutionId}?/clone method will be deprecated in a future release. Best practice is to begin using the new API methods to clone apps as soon as possible. 

    Closed Issues

    67093 / SCCORE-148

    NullReferenceException errors are generated when a large amount of Execution History is created in a short amount of time because there are a large number of Event Message apps being processed and the Connect on-premise agent cannot synchronize with the cloud. (Case # 65262,  01725410)


    If you select all flows in an app and attempt to delete them all at once, only some of the flows are deleted.(Case # 01806292)

    77588 / SCCORE-1513

    In some cases the Agent cannot synchronize Execution History with the Cloud. When the synchronization is not successful, error details cannot be seen in View Error Details and the app status remains at In Progress even though the job has completed. (Case # 01739741, 01773030)

    75257 / SCCORE-1548

    In the Query Block Properties Net Change tab,  if the field being used for Net Change is type datetime2  TIBCO Cloud Integration - Connect converts it to datetime when storing the date for the most recent record processed. The process of converting from datetime2 to datetime involves rounding the nanoseconds portion of the time value up or down to fit the value into the datetime field. This can cause a few records to be either reprocessed or skipped the next time the flow runs.  (Case # 70140, 01730258, 01889660 01934242)


    2019-02-26 07:11:16.2466667 is rounded up to 2019-02-26 07:11:16.247

    2019-02-26 07:11:16.2449990  is rounded down to 2019-02-26 07:11:16.243

    41553 / SCCORE-1945 / SCCORE-3095

    If you edit a Connection from within an app, the Agent used to test that Connection defaults to the first Agent alphabetically, which may not be the Agent selected for that app.

    SCCORE-2724 / SCCORE-6373

    App status remains In-Progress even though the app has completed. In some cases, execution history is not available for these apps. (Case # 01819986 01885642, 01886018, 01889561, 01891237)


    Enabled the Clear option on the Flow options menu on the App Details page to clear queued messages for Event flows. (Case # 02041258, 02044203, 02058587, 02062719)


    The status for an On Schedule app  sometimes displays as On Demand when not running instead of displaying Idle. (Case # 01850686, 01852373, 01853709, 01859358, 01862357, 01882119, 01908242)


    Appending records to a Lookup Table changes the sort order of the values in the User Interface. (Case # 01871348)


    A Scheduled or On Demand app remains in a Running status indefinitely and the number of records processed does not increase. Attempting to stop the app causes the state to stay in an In Progress or Stopping status. (Case # 01891602, 01894802, 01896296, 01898486, 01907510, 01909016, 01911382, 01911495, 01912313, 01912679, 01920760, 01921375)


    Improved the error message displayed in the Formula Editor when there is a data type mismatch. (Case # 01912532)


    If an app fails immediately, the date used for Net Change is updated even though no records were processed. (Case # 01913727)


    After testing the query in a Native Query Block you can only preview the data once.


    In some cases, Cloud Agents exceeded memory usage maximums and could not synchronize data with the Cloud or run apps. (Case # 01921869, 01921986)


    Occasionally Cloud Agents used with Request Reply flows that process a large number of messages can cause a degradation of cloud resources. (Case # 01921986)


    If there are several corrupted Connections in an Organization, Agents cannot synchronize with the Cloud. (01936682, 01940146)


    Deleting a Connection sometimes corrupts that Connection before the Agent can synchronize with the Cloud.  The Agent is unaware that the Connection no longer exists and attempts to use it, causing apps to remain in a Preparing state. ( 01936682, 01940146)


    If the flow Debug process fails with certain types of errors, such as an error caused by bad data returned from a Query, there is no way to exit the Debug process until it times out on its own.   (Case # 01931525, 01941061, 01941597, 01952448)


    Message flows that receive a large volume of messages occasionally leave messages in the queue because the completion notification for the last message processed is not received by the cloud, preventing subsequent messages from being processed. (Case # 01939306, 01941271, 01941069 )


    In some cases, apps that complete a run very quickly are stuck in a Running status even though they have executed successfully. ( Case # 01946236 01941759 )


    When working in the TIBCO Cloud Integration - Connect flow designer, the auto logout warning message displayed when the user has been idle is hidden behind the designer.  The user is logged out of TIBCO Cloud Integration but the flow designer continues to display. (Case # 01943902, 01948059)


    Configuring a Connection from within a flow for a Connector that only supports the Connect On-premise Agent, fails with an error because the Connection configuration dialog defaults to the Cloud Agent to test the connection. (Case #01946336)

    Error: Connection test failed: Connector is not installed on this Agent.


    If you change the agent on a TIBCO Cloud Integration - Connect app and then attempt to reprocess failed records, no error message is displayed and the records are not reprocessed.


    When you configure a new connection from within a flow, the first agent displayed alphabetically is used to test the connection instead of the agent assigned to the app. 


    The Find and Replace functionality in the Flow designer fails when searching for text that contains a period (.) and selecting either Names only or All. (Case # 02058641)


    When an agent has more that 100 configured connections, the Block Properties Formula Editor in a flow using that agent cannot display data for connections higher than the 100th and an error similar to the following displays:  (Case # 02058336)

    Message: Cannot read properties of null (reading 'indexOf')


    The TIBCO Cloud Integration - Connect POST /v1/orgs/{orgId}/solutions/{solutionId}/prepare method does not check for error conditions in metadata requests and continues the process, which eventually fails with an error similar to the following: Waiting for missing Field Metadata. (Case # 02050532)

    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...