TIBCO® Cloud Integration Release Notes

Last updated:
5:01am Sep 16, 2020

Sept 16, 2020

Release Notes

What's New 

This update is a maintenance release to close a couple of Known Issues and to provide you with some important updates and updated connectivity.

TIBCO BusinessWorks™ Plug-ins

  • CICS
  • IBM MQ
  • Salesforce

TIBCO Flogo® Connectors

  • Salesforce.com Einstein Analytics

Changes in Functionality

TIBCO Cloud Integration

  • The new Apps List Deployment column indicates where an app is deployed. In this scenario the agent/deployment definitions are as follows:
    • A TIBCO Cloud deployment indicates that apps are executed in the  TIBCO Cloud.
    • A Hybrid deployment indicates that apps are executed on a server that is not managed by TIBCO. This can be a local server or other infrastructure. 
    • None indicates that the app has been configured in the TIBCO Cloud but is not running. 
  • TIBCO Cloud Integration - Connect apps with an Incomplete or Disabled status are not included in App Totals on the Dashboard. 

TIBCO Cloud Integration - Connect Agent

  • TIBCO Cloud Integration - Connect Agents displayed on the Agents page have been renamed as follows: 
    • Cloud Agent is now Connect Cloud Agent
    • On-Premise Agent is now Connect On-Premise Agent


When a Flogo app is created from a Swagger API specification, Flogo REST Trigger and flows are now auto-configured with trigger and flow input/output mappings and, wherever applicable, with Return and Configure HTTP Response activities.

TIBCO Cloud Live Apps

When working with TIBCO Cloud Live Apps and connected TIBCO Flogo apps that share API calls, you may need to remap the calls after the following changes to the Flogo app:

- Copying the app from one subscription to another

- Pushing the app with a new set of properties

- Moving the app from one organization to another

- Exporting and re-importing the app

- Pushing the app after the latest upgrade to TIBCO Flogo itself

In all cases, running integrations of TIBCO Cloud Live Apps and TIBCO Flogo are not affected, but after opening the app in TIBCO Cloud Live Apps, you must perform the remapping.

TIBCO Flogo®

  • The Flogo app start timeout has been reduced from 10 minutes to 3 minutes. 
  • When a new trigger is added, for GET, DELETE methods, the Response Schema configuration is enabled instead of the Request Schema.

    When a new trigger is added, for POST, PUT methods, both the Request Schema and the Response Schema configurations are enabled.
  • To support BusinessWorks consumers, the swagger for Flogo service is generated as per specification. If a Flogo app has been running for a  long time, you need to re-push the app.
  • TIBCO Cloud - Proxy Agent must be connected to scale up Hybrid Connectivity enabled Flogo apps.

TIBCO Cloud Integration

  • The Last Run column on the Apps List has been renamed Last Started to indicate when an app has been executed or scaled up from 0 to 1 or more instances.
  • The default time range for displaying app logs on the App Details Logs tab is now set to 5 minutes instead of Realtime.When you create a new app in the Web UI, the app won’t automatically start. You can continue to design or customize your app, then scale it up and start it when you’re ready.
  • When adding an on-premises database through the Proxy Agent with a Flogo app, you must now push the app after it was designed, add an access key, then re-push the app and scale it up to start the app running. Previously, it was possible to scale and start the app before the access key was added.
  • When you create a new app, there is no longer an option to name your app in the Create App dialog.  Apps are created with a temporary name such as `New_Flogo_App_0`, `New_Flogo_App_1`, and so on. You can then rename the app later. 
  • When creating a new app, the option to name that app is not available until you reach the App Details page, then you can edit the text in the name field. 
  • Modifying an app name or description does not generate a Success message, however the information is saved. 
  • The timezone is no longer displayed on dates in the Apps list or the App Details page. The times shown are in your local timezone.
  • App build log messages no longer display in the app logs. 
  • The shortcut menu option for app deployment changed from Mark as Draft or Mark as Live to Set deployment stage. (This is also true for the same option on the Apps page.)
  • You can start and stop apps from the Apps page, but scaling controls are now only available on the App Details page.
  • There is no longer a success notification message in the Web UI when an app scales up or down.

TIBCO BusinessWorks™

For TIBCO BusinessWorks applications that connect to Oracle database and require Oracle JDBC Thin Driver supplement: when deploying new apps or re-deploying existing apps to TIBCO Cloud Integration, generate the manifest.json file and supplement the Oracle JDBC Thin Driver again before pushing the app to TIBCO Cloud Integration. 

For TIBCO BusinessWorks Plug-ins that require third-party drivers, JARs or libraries to be supplemented in TIBCO Cloud Integration using TIBCO Cloud™ – Command Line Interface bwplugin supplement command: when deploying new apps or re-deploying existing apps to TIBCO Cloud Integration, supplement the respective third-party drivers, JARs or libraries again before pushing the app to TIBCO Cloud Integration.

Some Plug-ins may require repackaging of supplements. Refer to the respective Plug-in documentation for more information.


  • These actions are not required for existing running apps.
  • Supplementing TIBCO EMS libraries is not required.

API Mock Apps

API Mock apps have been moved to APIs under My TIBCO Cloud Capabilities. They can still be accessed using the TIBCO Cloud™ – Command Line Interface, however those options will be removed in a future release.

TIBCO Cloud Mesh

When you create a REST service binding, Studio generates a default name and path for the service, "Resource" and "/resource" respectively. When deployed to TCI, these names appear in generated Swagger metadata for the endpoint. If left unchanged, all services deployed in this way appear indistinguishable in TIBCO Cloud Mesh. Therefore, it is a good idea to immediately give any new service binding a more specific name and path. " 

TIBCO Flogo®

Validation Improvements

● In prior releases, flows on the flow list page were validated automatically. Now, you need to manually validate the flows.

● In prior releases, on editing an activity, the entire flow was validated automatically. Now, only that particular activity is validated automatically.

Revalidating an app after navigating into a flow

After validating an app, if you navigate into a flow, you must validate the app again irrespective of whether you made changes to the flow or not. Flogo Enterprise does not retain the results of any previous validation.

Timeout field of InvokeRESTService activity

The unit of measurement for the Timeout field in the InvokeRESTService activity has been changed to milliseconds. You might want to reconfigure this field using milliseconds and deploy the app again.

Changes in user interface

The following changes have been made to the user interface:

● Flows list page

— The App Properties Button has been renamed to Properties.

— The Revert to last push, Import, and Export buttons have been moved into a list menu.

- Push app button has been renamed to Push

● Flow Canvas/Details page

— The Start testing button is renamed to Test.

— The Revert to last push button is removed.

— The Properties button has been added for specifying app properties.

— Push app button is removed.

● Buttons have been rearranged to group primary actions together and secondary actions together.

TIBCO Flogo®

Explicit save for activity and trigger configuration

If you make any changes to the schema that you entered when creating a trigger, you must save the changes explicitly by clicking Save and then propagate the changes to the flow input and flow output. If you have made changes to the schema, but do not save the changes explicitly by clicking Save, a warning message is displayed asking you to first save the changes before the schema can be synchronized.

Deprecating and End Of Support for Development Tools


Support for TCI_BW_LOGGER_OVERRIDES and TCI_BW_CONFIG_OVERRIDES variables has been removed from TIBCO Cloud Integration.

Use the BW_LOGGER_OVERRIDES and CUSTOM_ENGINE_PROPERTY variables under Environment Controls -> Engine variable in the TIBCO Cloud Integration User Interface to set logger and custom engine properties respectively. Additionally use the Add engine variable feature to add the engine properties for BusinessWorks apps.


App log monitoring will no longer be supported for versions of TIBCO Cloud™ – Command Line Interface prior to version 2.4. If you downloaded TIBCO Cloud™ – Command Line Interface before April 2019, you should download a new copy from the Download page in TIBCO Cloud™ Integration.

Migration and Compatibility

TIBCO Flogo®

  • Importing an app created in a prior version of TIBCO Cloud Integration or Flogo Enterprise that uses a REST Trigger and is configured with an HTTP response code breaks trigger reply mappings. To fix this issue, export the app from the latest version and import it again. 
  • For older apps, in some cases, mappings done at parent level are displayed at the element level after import. Note that it does not have any impact at runtime.

TIBCO Flogo®  Connector for Amazon DynamoDB

  • After importing a Flogo app into TIBCO Cloud Integration that uses a Flogo Connector for Amazon DynamoDB Query activity, the Output Schema in the OutputSettings section is empty and you will need to reconfigure the schema.

TIBCO Flogo®  Connector for Salesforce

For older apps imported with the latest Salesforce connector version, users can see one more new field in the Salesforce connection,  "WI_STUDIO_OATH_CONNECTOR_INFO".

TIBCO Flogo® Connector for Salesforce.com Einstein Analytics

Salesforce connections with Custom OAuth2 Credentials set to True are not supported for the Salesforce Einstein Analytics connector.

TIBCO Flogo® Connector for Zuora

If a Zuora app is created in a prior version of Flogo Enterprise and is then imported to the current release, mapping issues are observed in the Input tab of the Zuora Subscription Activity for the Create Subscription operation.

Export the same app without making any changes and then import it again.

TIBCO Cloud™ Live Apps

TIBCO Cloud Live Apps integrations using TIBCO Cloud Integration apps will continue to run without incident, until you make any changes in the service activity in the Live App.  At that time, you must rescale the TIBCO Cloud Integration app before redeploying the Live App; scale the TIBCO Cloud Integration app up one instance and down again, to avoid any interruption in service.

TIBCO Flogo / TIBCO BusinessWorks

When using TIBCO Cloud Mesh from a TIBCO Flogo  or TIBCO BusinessWorks app to call another TIBCO Cloud Integration app that was deployed prior to the release May 2020 release of TIBCO Cloud Integration, that target app must be rescaled to enable the calling app to run successfully. Scale the target app up one instance, then down again, to avoid service interruption. This rescale is a one-time requirement to enable the target app for TIBCO Cloud Mesh use.

Closed Issues


The TIBCO Businessworks Active Database Plug-in Data Event Poller Activity does not auto-start polling messages until an app is restarted. This is caused by the frequent disconnect with the database due to some network issue.


The SapHanaDatabaseJdbcSQLException was caught in the catch block but the field data for msg and msgCode fields did not get populated. For an existing project, delete the catch block, change any field and save the activity to update the fault tab. Add the catch block again.


Support for Import From CONTROL FILE statement:

To use this feature, in the SAP HANA Database Insert activity, select the 'Use Import From' checkbox and the 'Import File Type' as 'CONTROL FILE'. The Control file to be imported, must exist either on the HANA Server or be available in a folder visible to the HANA Server.


After  the May 2020 TIBCO Cloud Integration upgrade, the names of some existing connections are not displayed in the connection list.


The  IDocListener activity on the TIBCO BusinessWorks SAP Plugin palette does not provide any configuration for a connection retry to the TIBCO Enterprise Message Service server.


TIBCO BusinessWorks™ apps with a Salesforce connection  fail at runtime with errors similar to the following: SFWaveUpload_Upsert'[github.com/project-flogo/legacybridge] - Get salesforce token from connection field error [invalid character '=' looking for beginning of value]

Known Issues

IPAS-530 / IPAS-9437

Summary: TIBCO® Cloud Integration does not support user-defined SSL parameters for their application. While TIBCO Business Studio™ - Cloud Edition does not stop you from creating an SSL Server Configuration Shared Resource, this resource, if created will be ignored during the application deployment. (Case # 01236070, 01236703, 01685369)

Workaround: Instead of user-defined SSL parameters, use Mashery endpoint configuration. Mashery can host SSL certificates and ensure SSL/TLS connection encryption on your chosen domain or host. 


Summary: If the imported API specification contains a content type other than application/json or application/xml, the content type does not display.

Workaround: None


Summary: The required check-box is not added for the body parameter, therefore, you cannot use it to specify whether the body parameter is required as other parameters.

Workaround: None


Summary: The Marketo plug-in uses absolute file paths in some of the activities. Due to the nature of TIBCO Cloud Integration these activities are not supported

Workaround: None


Summary: After implementing a Swagger specification that has a “basePath” element in the specification the API tester functionality does not work correctly.

Workaround: Manually remove the “basePath” element prior to implementing it in TIBCO Business Studio™ - Cloud Edition. This does not affect the API specifications created in the API Modeler in TIBCO Cloud Integration.


Summary: The JavaScript code to implement advanced mock responses is not automatically saved

Workaround: To ensure the code is not lost, save the JavaScript code prior to changing methods.


Summary: The API documentation generated from TIBCO Business Studio™ - Cloud Edition which is used to display the endpoints in the API tester will contain all endpoints that are present in the API specification used when implementing the project. The original API specification is passed along to the runtime and does not take into account any non-implemented operations.

Workaround: None


Summary: Two-way SSL Authentication is not supported when using the Salesforce Outbound Listener and the Microsoft Dynamics CRM Entity Event Source Activity. This is because you cannot add your own authentication resources (see IPAS-530).

Workaround: None


Summary: Using XML reserved characters in application properties will result in those overridden values being ignored.

Workaround: None


Summary: On Macintosh systems only: Launching TIBCO Business Studio™ - Cloud Edition by double-clicking TIBCOBusinessStudio.app intermittently fails if Java 6 is not installed on your system


1. Right-click TIBCOBusinessStudio.app and select 'Show Package Contents'

2. Run TIBCOBusinessStudio executable under Contents-> MaCOS folder


Summary: When editing a Microflow App, if you do not push the edited application, you will still be able to scale up the application, which will fail, since the updates are not pushed to the runtime yet.

Workaround: Always push any changes on a MicroFlow App before scaling


Summary: Amazon S3 plug-in does not support relative paths. Hence file type is not supported in the Put and GetObject activities

Workaround: None


Summary: The resource name of an API spec is used as the basepath in the URL for REST endpoints that are generated by TIBCO Business Studio™ - Cloud Edition. This causes an inconsistency between the Mock endpoint URL and TIBCO Business Studio™ - Cloud Edition URL when a Mock application is replaced with integration application. This will also have an impact on a Microflow application created based on the Mock application that has been replaced. The Microflow application will need to be re-created based on the new integration application.

Workaround: None


Summary: Installation fails with an Ant task error when TIBCO Business Studio™- Cloud Edition is installed on top of an existing installation with the same version.

Workaround: Uninstall the old TIBCO Business Studio™ - Cloud Edition before installing the new TIBCO Business Studio™ - Cloud Edition or install the new TIBCO Business Studio™ - Cloud Edition in a new TIBCO_HOME.


Summary: The following activities in the TIBCO MDM projects are not supported for TIBCO Business Studio™ - Cloud Edition as the relative path does not work:

File type attributes

Upload Datasource activity

Text search activity

Upload and Import activity

Workaround: The recommended approach to build TIBCO MDM projects and work with these specific activities is to use TIBCO® MDM Studio.


Summary: In the TIBCO Business Studio™ design time, the Test Connection feature for Email Palette shows success even though you have selected plain port with TLS enabled and TLS Port without TLS enabled combination.

Workaround: None. Even though the design time does not throw any error, you will a failure during runtime.


Summary: Process Implementation/Process Diagram is not visible in the TIBCO Cloud™ Integration user interface, if the Integration (BusinessWorks) application process package name contains dot(.) or hyphen(-) in its name.

Workaround: Remove the dot(.) or hyphen(-) from the process package name and regenerate the ear and repush the application.IPAS-3979

Summary: When mutual authentication is enabled, SSL test connection fails in TIBCO Business StudioTM - Cloud Edition.

Workaround: None


Summary: In Web Integrator, when a RESTTrigger is created from a schema or JSON sample data containing Date and DateTime type attributes, the Date and DateTime DataTypes are shown as a string in the output tab of POST/PUT Operations and Input of ReplyToHTTPMessage Activity. Also, for the double data type, is shown as a number, and the null data type is shown as a blank icon in the mapping input tab.

Workaround: None


Summary: When an app with VPN connection is promoted to an operational sandbox , a new promoted app is created with 0 state. The VPN connection status for this promoted app is - "/0 instances connected" which is incorrect.

Workaround: Scaling up the promoted app will bring up the VPN status to normal.


Summary: Currently, the Salesforce Wave Analytics connector does not support mm/dd/yyyy (using a “/” delimiter) format in the date type.

Workaround: Use other date formats, such as mm-dd-yyyy (using a dash as the delimiter) instead.


Summary: If a record does not have any input, the Salesforce Wave Analytics connector throws "interface conversion: interface {} is nil, not map[string]interface {}exception."

Workaround: None.


Summary: When a Node.js app is started, the value in the service.json file cannot be retrieved.

Workaround: Update the parameters in the User Interface and update the app.


Summary: If using a MongoDB connection shared resource, use a host port number between 1024-9999.

Workaround: None


Summary: If your BusinessWorks application contains a string of type Password and is more than 63 characters in length, you are unable to successfully deploy the application.

Workaround: Make sure the password has fewer than 63 characters.


Summary: When clicking a REST endpoint that invokes a service If the project for that service contains credential mapping policy, it results in an error.

Workaround: None



If the REST Service is implemented with HEAD/OPTIONS method, then from Swagger UI, it is not possible to invoke these operations.

WorkAround: None


Summary: Set to Default is not available in the Environment control tab for password type app property.

Workaround: None

IPAS 8860

Summary: The endpoint URL formed in TIBCO Cloud Integration for OData service is incorrect.

Workaround: Manually edit the endpoint URL for OData in TIBCO Cloud Integration by replacing the special character "%2F" with "/"

in the URL and appending the application name and the OData resource name to the URL. For example, if the endpoint URL were  https://localdev-integration.cloud.tibcoapps.com:97/plf7pbumdgul74wsuhl3... you must edit it to https://localdev-integration.cloud.tibcoapps.com:97/plf7pbumdgul74wsuhl3...


Summary: For any TIBCO BusinessWorks plug-in that requires supplement in TCI, if the supplement was pushed prior to version upgrade of plug-in, then any subsequent application push containing that plug-in will fail.

Workaround: Re-push the respective supplements for the plug-ins used in the application.


Summary: After renaming the app, the new name is not reflected on API Tester.

Workaround: Repush the app


Summary: When you open a Mock app not owned by you, and proceed into the "Advanced Mock Response" page, you are still able to edit the response code and the "Update Mock App" button is still enabled, even though nothing happens when you click the button.

Workaround: None


Summary: In TIBCO CloudTM  Integration,  if you copy an app, the history for the original app is not carried forward for the new app. 

Workaround: None.


Summary: When using the app list or app detail command from the TIBCO CloudTM– Command Line Interface, the information returned displays N/A for the app version number.

Workaround: None.   


Summary:  In the Swagger API test page, TIBCO Flogo® apps with REST trigger  with Response Codes set to True do not display all response headers in the Swagger UI. 

Workaround: None.


Summary:  In TIBCO CloudTM Integration, REST apps with Response Codes set to True do not display response headers in the User Interface for POST methods. 

Workaround: None.


Summary: The gRPC trigger in TIBCO Flogo® apps is not supported on TIBCO CloudTM Integration.

Workaround: None.


Summary: Any TIBCO Flogo activity that requires connectivity to an on-premises service does not work in Flow Tester.

Workaround: None.


Summary:  TIBCO Flogo® app properties do not work with the port field on REST and Graphql triggers.

Workaround: Port does not support app property, manually change the port when needed.


Summary: When replacing a TIBCO Cloud™ Integration - API Mock App, if the DB service is enabled, it  is listed as a source app on the Replace App dialog..

Workaround: None. The DB service app should not be a source when replacing any type of app. 


Summary: Pushing a TIBCO BusinessWorks™ app and configuring hybrid connectivity from the UI takes a long time. In addition, changing the hybrid connectivity access key for a scaled app fails with an error similar to the following:  

 "[ERROR] the supplied credentials cannot be used to access the specified tunnel endpoint"

Workaround: Use the TIBCO Cloud™ – Command Line Interface to push the app and change the access key. 


Summary: CertainTIBCO Business Studio™ for BusinessWorks™ Apache Kafka plug-in apps that require SSL certificates can fail with an SSLHandshake Error similar to the following: java.security.cert.CertPathValidatorException: Algorithm constraints check failed on keysize limits. RSA 1024bit key used with certificate

Workaround: Use public certificates with RSA keysize set to 2048. Use of certificates with RSA key set to 1024 is not a best practice.


Summary:  If an app detaches from a shared access key, app logs for the remaining apps being streamed using the logstream command lose several seconds of log information.

Workaround: None.  


Summary: Apps using an on-premise database via the TIBCO Cloud™ - Proxy Agent cannot connect to the database when another app is detached from the same accessKey.

Workaround: When the app completes being detached from the accessKey, database access resumes. 


Summary: When using the  logstream command for the TIBCO Cloud Integration -  Command Line Interface  streams app logs via the TIBCO Cloud™ - Proxy Agent,  TIBCO ActiveMatrix

BusinessWorksTM Plug-in for Apache Kafka  logs are received intermittently and the set of log files is incomplete. 

Workaround: None. 


Summary: Pushing a nodejs app with a redirect to a  private endpoint causes backend redirects to be disabled. 

Workaround: None.


Summary: When a user has the Apps list displayed and an app is deleted using the TIBCO Cloud™ – Command Line Interface or some other method, if that user attempts to delete or make any change to the app using the User Interface, the change is not made and there is no message displayed to indicate that the app has been deleted. 

Workaround: None.


Summary: If you copy an app from the App Details page, the User Interface remains on the App Details page and does not go to the Apps list as expected.

Workaround: Manually navigate to the Apps list to locate the new app. 


Summary: When generating an ear file and manifest file for deployment, the port value from the module property in the shared module is not included, causing an error when using the manifest file to push the app to the Cloud. 

Workaround: Manually update the port field in the manifest.json file to port 80.


Summary: On the Apps list, the Set Endpoint Visibility menu option is available for apps without endpoints. 

Workaround: None.


Summary: Deployment Stage and Endpoint Visibility status icons do not display in App Details for users with either a Read-Only or User role who are not the owner of the app.

Workaround: Refer to the History and Endpoints tabs for that information.  


Summary: When accessing the Apps list, cached app statuses sometimes display briefly before being refreshed. 

Workaround: The page will refresh after a few seconds. 


 Summary: When apps are pushed or re-pushed using the TIBCO Cloud™ – Command Line Interface and TIBCO Businessworks Studio, the status "Scaling" is never shown on the User Interface only the "Running" status is displayed. 

Workaround: This is due to a delay in refreshing the User Interface for apps pushed from the TIBCO Cloud™ – Command Line Interface. Wait a few moments and the status will update in the User Interface. 


Summary: On the App Details Endpoints tab, if you are in the API tester User Interface the API version and Base URL are not displayed. 

Workaround: See the Base URL on the Endpoints tab and download the API spec to see the version number. 


Summary: On the Apps list the Stop action button is displayed for a failed app instead of the Run action button.

Workaround: Go to the App Details page and scale the app. 


Summary: On the App Details Endpoints tab, if you are in the API tester User Interface it is not refreshed when you perform any of the following actions on an app: scale up/down, replace, or change endpoint visibility. 

Workaround: Move to another tab and come to the Endpoints tab.


Summary: On the App Details Endpoints tab, the API tester does not open for complex schemas where there are mixed array types in request or response schemas.

Workaround: None.


Summary: Apps shown in the Apps list cannot be sorted by Status or by Name.

Workaround:  If you are searching for a specific app, use the Search field to search by Name. 


Summary: Occasionally, the total number of log messages displayed on the App Details Logs tab is incorrect.

Workaround: None.


Summary: If you copy or replace an app from the App Details History tab, the content on the History tab is not updated automatically with new information.

Workaround: Move to another tab and come back to the History tab to refresh and display the new content. 


Summary: In TIBCO Cloud Integration - Connect, the Since Yesterday filter on the App Details Execution History tab requests data for the past 24 hours using the local time setting on your computer instead of UTC time, but Execution History is stored in UTC time. Depending on your local time setting the list of results may exceed the past 24 hours or be less than the past 24 hours.  

Workaround: Use a different filter and sort by the Start column to see the most recent executions of the selected app. 


Summary:  Application variables do not retain changed values after an app is re-pushed.

Workaround: Enter them again each time you push the app. 


Summary: In App Details on the Logs tab, when selecting a custom date time filter the am/pm portion of the date/time field is not updated correctly. This issue affects both the log filters and the download logs dialog.  

Workaround: Manually, enter the am or pm in the text field. 


Summary: When downloading either the TIBCO Cloud - Command Line Interface or TIBCO BusinessWorks, the platform is not detected automatically.

Workaround:  Select the download platform manually from the drop-down.


Summary:  When switching between the Apps List and the App Details for an app, the app instance number displayed sometimes does not match. 

Workaround: The number will refresh after a few seconds and display correctly. 


Summary: In some cases, the App Peek option is disabled on the Apps list for apps with an error status. 

Workaround: None. 


Summary: For apps created prior to the May 2020 TIBCO Cloud Integration upgrade, the app instance count on the Apps Dashboard does not match the actual app instance count. 

Workaround: Re-push the apps. 


Summary: Empty apps created prior to the May 2020 TIBCO Cloud Integration upgrade do not display in the Apps list, however, because they still exist their names cannot be reused in a new app. 

Workaround: Delete the app using the TIBCO CloudTM– Command Line Interface. 


Summary: App Monitoring and App Peek data does not include apps created prior to the May 2020 TIBCO Cloud Integration upgrade until those apps are re-pushed. 

Workaround: Flogo apps can be re-pushed from the User Interface. BusinessWorks and Node.js need to be re-pushed from the TIBCO CloudTM– Command Line Interface.


Summary: When API Mock apps are scaled using the TIBCO CloudTM– Command Line Interface, the number of instances displayed is higher than the number requested during the scaling process. 

Workaround: None. 


Summary: App name is displayed instead of organization  name when a BusinessWorks app is copied in TIBCO Cloud Integration. 

Workaround: None.


Summary: When working in TIBCO Cloud Integration, if you click a link or a button that opens a dialog, such as the Flow editor or a Connection dialog, that dialog sometimes ends up behind the browser. 

Workaround: Minimize the browser to locate the dialog and continue working.


Summary: Log Activity is not always being logged for TIBCO Cloud Integration apps when logs are within the Loop feature.

Workaround: Move the logs outside the Loop. 


Summary: When a User changes Connection information, such as credentials used to connect to an external source, these changes will not propagate to existing app instances using that connection. 

Workaround: Repush the app instances to pick up new connection modifications.


Summary:  App Details tabs become unresponsive after clicking the Monitoring tab for Flogo apps that only have a trigger without activities in the flow.

Workaround: Add activities in the flow. 


Summary: Updates to app names sometimes do not display on the Apps List page immediately.

Workaround: Leave the Apps List page and go back to it, which forces the page to refresh. 


Summary: In the App Details for a TIBCO Cloud Integration - Connect On event app, there is a delay in displaying a value in the Messages column.

Workaround: None. The column is updated after several seconds. 


Summary: In some cases, if you reconfigure a BusinessWorks  app such that some app properties are deleted, when repushing the app an error similar to the following is generated that references the deleted properties.  Detail: Error while updating application configuration : Cannot override properties because one or more of those properties is not set for that application. 

Workaround: Use the TIBCO Cloud Integration - Command Line Interface to change or push the new property values. .


Summary: Changes to the entities selected in the Select Entities dialog in a Data replication app are retained whether you use the Cancel or Save button at the bottom of the dialog, but are lost if you do not click Save in the Entities section of the Data replication app. 

Workaround: Be sure to click Save in the Entities section of the Data replication app. 


Summary: If you reset metadata for a Connection used in a Data replication app and the data set returned is very large, when you open the Manually Selected option in the app to select the entities for replication, the dialog is blank.

Workaround: Close the dialog and wait a few minutes until the metadata reset is complete, then open the Manually Selected option again to display the list of entities.  


Summary: The Last Started column on the Apps List does not automatically refresh if the app was re-pushed from the TIBCO CloudTM– Command Line Interface.

Workaround: Refresh the Apps List page.


Summary: When you copy an app, if that source app is in a failure state, the failing app is rescaled. 

Workaround: None.


Summary: The stop timeout for BusinessWorks apps has been increased to 60 seconds. Existing or older apps that have already been pushed, take the full 60 second stopTimeout when stopped. 

Workaround: None.


Summary: If an app is in a Failed status before the TIBCO Cloud Integration July 8, 2020 upgrade,  then after upgrade when the cause of the failure is fixed, the Last Started date does not display on the App List page. 

Workaround: Restart the running app to show the Last Started date.


Summary:  If you select an access key for a Hybrid Database Connection, the user interface does not allow you to immediately choose a different one. 

Workaround: None. 


Summary: In TIBCO Cloud Integration - Connect, the Today filter on the App Details Execution History tab requests data for the past 1 hour using the local time setting on your computer instead of UTC time, but Execution History is stored in UTC time. Depending on your local time setting the list of results may exceed the past 1 hour or be less than the past 1 hour.  

Workaround: Use a different filter and sort by the Start column to see the most recent executions of the selected app. 


Summary: Context-sensitive help is currently not available for Activity on the BusinessWorks palette.

Workaround: None.


Summary: The Hybrid agent executable, tibagent.exe, does not run on a Windows platform if the debug option is used. 

Workaround: None. 


Summary: A Cloud app and a Remote app could end up with the same name and both display on the Apps List page.

Workaround: None. 


Summary: The App list and Environment & Tools pages do not store user preferences when the  Hybrid filter is selected. When you leave one of those pages and return, the page is refreshed. 

Workaround: None. 


Summary: In the App Details Monitoring tab, the “Last 2 hrs” filter is selected by default. If no app executions have occurred since the latest TIBCO Cloud Integration upgrade, no data is shown on the graph. Execution data for the last 24 hours can be displayed only when the “Last 24 hrs” filter is selected. 

Workaround: Select the “Last 24 hrs” filter to see previous data plotted on the graph. 





Summary: The output of the "current-dateTime()" function is not the same when the function is used in TIBCO Cloud Integration  and TIBCO Business StudioTM.

Workaround: None.


Summary: TIBCO Cloud Integration is unable to monitor the TIBCO BusinessWorks Container Edition remote apps with a hybrid agent for hybrid monitoring when those apps are running in a  Windows container.

Workaround: None. 









Summary: Creating a new Event or updating an existing event in the S3 Bucket Event Lambda trigger and re-pushing the app deletes existing Events on AWS S3.

Workaround: None.


Summary: You cannot export app properties from a binary that has an API Gateway or S3 trigger.

Workaround: None


Summary: When uploading a custom schema for GraphQL, if the custom schema has a cyclic dependency, the following error is returned and the upload fails:

Maximum call stack size exceeded for circular reference

Workaround: None


Summary: Depending on your machine configuration and browser configuration, you might not be able to upload a large Swagger API definition JSON file or the browser might become unresponsive. The following error message is displayed on the Network tab and the file is not uploaded:

Request entity too large

Workaround: None


Summary:TIBCO Flogo® does not support uploading Swagger specification definitions that have a cyclic dependency.

Workaround: None


Summary: You run into an error after an old application JSON file is imported if it uses the default REST Invoke activity.

Workaround: Import the application and delete existing default REST Invoke activity and add new REST Invoke activity from the Default category.


Summary: If a Kafka producer produces a JSON string, the Kafka consumer does not receive any data.

Workaround: None


Summary: If a field in the mapper of an activity is mandatory and you have not provided a value, an error is not displayed on the activity or flow canvas.

Workaround: None.


Summary: When configuring response code in a REST Trigger, Response Body and Response Headers must follow same input schema type.

Workaround:  Response Body and Response Headers must be the same type, either JSON Data or JSON Schema. 

Workaround: Do not use ConfigureHTTPResponse in the RESTInvoke Flow.


Summary: An extra element is added as a null value for any missing elements in an array when doing array mapping. For example, if there is an array where the first element has 3 fields and the second element has only 1 field, another 2 fields are added with null values for the second element.

Workarund: None.


Summary: When Project Flogo apps are imported into Flogo, the Input/Output mappings are lost after the Sync Schema option is used.

Workaround: None.FLOGO-4136

Summary: Overriding certificate variables for SSL connections under App > Environment Variable causes Flogo App updates to fail.

Workaround: None


Summary: Getting duplicate proto type registered message while starting gRPC app binary which has gRPC trigger and gRPC activity using the same proto file.

Workaround: Change the package name to a different one to make sure gRPC trigger and gRPC activity use the different package name in proto file.


Summary: When an app with different trigger and handler settings is imported, trigger and handler settings are not replaced after selective import.

Workaround: None


Summary: When an Apache Kafka app created in a previous release is imported in the current release, and you click Edit in the Connections tab, the Use Schema Registry option is not available in the Apache Kafka Client Configuration dialog box.

Workaround: Create a new connection and use the connection in the app.


Summary: An activity throws a mapper error if the mapped object does not exist, as the FLOGO_MAPPING_SKIP_MISSING environment variable cannot be set in the flow tester.

Workaround: None


Summary: When using the isdefined() function in a mapper, if you want to validate whether an array is empty or not, on clicking the array in the Activity Input section on the left side, array.foreach() appears in the mapper on the right side and it fails at runtime.

Workaround: Remove array.foreach() manually and run the app. 


Summary: For the TIBCO Cloud™ Messaging service, if you have configured both the Durable Subscriber and the Content Matcher options, changing the value of the Content Matcher for an app that has already been pushed, causes repushing the app to fail.

Workaround: None


Summary: If changes are made to a Swagger specification file and the file is saved with a different name, the changes are not reflected in the app even if you click the Sync Schema button. 

Workaround: None     


Summary:  When using a  field name that contains special characters, the array.foreach mapping fails with an error similar to the following: "eval expression failed to resolve Loop: 'field name', ensure that Loop is configured in the application".

Workaround: Add a scope name before field name, such as manually changing $loop["fieldName"] to $loop["ScopeName"]["fieldName"]   


Summary: Single quotes are not supported in TIBCO Flogo mapper variables.

Workaround: None.


Summary: If required elements of a request schema are not provided, the runtime provides a response but the tester returns a validation error.

Workaround: None


Summary: Anonymous arrays are not supported in TIBCO Cloud Messaging.

Workaround: None


Summary: Multi-dimensional arrays are not supported in TIBCO Cloud Messaging.

Workaround: None


Summary: Boolean type and null data type are not supported in TIBCO Cloud Messaging.

Workaround: None


Summary: For the ReceiveHTTPMessage trigger and InvokeRestService service, you cannot select an app-level schema if the trigger or activity has multiple responses.

Workaround: None


Summary: If you add the wrong data in the input mapper, an error symbol is not displayed on the activity. The error symbol is, however, correctly displayed in the input mapper section.

Workaround: None


Summary: Not able to refresh service automatically from TIBCO Cloud Mesh in Rest Invoke Activity.

Workaround: Do one of the following: 

  • Select another service and switch back to the original one
  • Change the timeout field to any other value and change back
  • Modify any field value under Settings, which will pick up new changes from TIBCO Cloud Mesh


Summary: Flogo ConfigureHTTPResponse activities do not correctly update when reply settings are changed.

Workaround: Trigger save by re-doing or undoing some of the mapper mappings on the HTTPResponse activity.


Summary: Not able to invoke BusinessWorks service returning string response through InvokeRestService.

Workaround: None 


Summary: While configuring Invoke REST activity with a service from TIBCO Cloud Mesh, you might see a duplicate service name for existing service(s) with multiple endpoints.

Workaround: Repush the Flogo service app. 


Summary: While adding elements in the array.flatten() function, the mapper becomes slow and the page becomes unresponsive after some time.

Workaround: None


Summary: For Flogo apps with no public endpoints, such as apps with triggers other than REST or GraphQL, the set endpoint visibility option displays in the User Interface.

Workaround: This can be ignored.


Summary: While running an app in flow tester, if you provide a JSON schema with a nested array, it returns an error at design time.

Workaround: None


Summary:  When the ownership of a Flogo app is changed or the app is replaced, the available actions listed on the App Details page are not refreshed automatically.

Workaround: Refresh the page or navigate to the Apps list and open App Details again.


Summary: When creating a new trigger, you cannot use the Bind an application property button to bind a property to the port.

Workaround: None


Summary: If connection details, such as credentials, are changed in any OAUTH connector, such as Salesforce, then any running apps using that connection do not pick up the change.

Workaround: Repush the app, to pick the connection changes.


Summary: After  the May 2020 TIBCO Cloud Integration upgrade, the names of some existing connections are not displayed in the connection list.

Workaround: Edit the connection and click Save to display the connection name. 


Summary: If you copy an app from another organization, the Swagger schema switches to the embedded schema when the app is re-pushed the first time.

Workaround: Re-push the app one more time.


Summary: The following error is displayed when the service called in the InvokeRestService activity is re-pushed after upgrade: 'Service has been updated in TIBCO Cloud Mesh, please reconfigure this activity.'

Workaround:   Select another service and then the main service to remove the error and then select the required path and method. Note that at runtime app works correctly even with this design time validation error.


Summary: When a Flogo app is copied to another organization and run, if you repush the app, the Swagger checksum changes, which breaks the integration with TIBCO CloudTM Live Apps.

Workaround: None.


Summary:  In TIBCO Flogo, sometimes the datetime.currentDate() cannot be formatted or parsed  by the datatime.parse or datatime.formatDate() function.

Workaround: Select one of the following options: 

  • Note that datetime.currentDate() is deprecated. Instead use datetime.now().
  • Remove +00:00 from datetime.currentDate() in the string.substring function when it is used to format or parse. string.substringBefore(datetime.currentDate(), "+")


Summary: On the InvokeRestService activity, the app level schema toggle should not be displayed for plain/text and other request/response types.

Workaround: None. 


Summary: In TIBCO Flogo, when app ownership is transferred to a Read-Only user, passwords are not preserved. 

Workaround: None.


Summary:  Flogo apps fail to scale if you update Engine Variables before pushing an app.

Workaround: Flogo apps must be pushed at least once before scaling up.


Summary: For a Flogo app pushed using the TIBCO Cloud Integration - Command Line Interface, the connection is not shown in your flow activities if the associated connection is not already present in the Connections page in the TIBCO Cloud Integration user interface.

Workaround: None. Since the app implementation is read-only, you do not need to select the missing connection in your flow activities. At runtime, it does not report any errors.


Summary: Multiplying a float64 with a json.number generates a runtime  error when using a multiply operation in mapper for the number field.

Workaround: Use the coerce.Float64() function to convert the number field to a float64 and then use the float64 to  multiply.


Summary: For DBConnectors (MySQL,Postgres, SQLServer,Oracle) when manual mode is switched to true, if you enter a query and click the fetch button, the table is populated with metadata. After that, when you click the Add row button, all previous metadata disappears.


1. Switch manual mode to true.

2. Enter a query and click the Fetch button.

3. See that the table gets populated with metadata.

4. Click the Save button.

5. Switch between activities tabs.

6. Click Add row in manual mode.

7. Verify that the new row appears along with other metadata.


Summary: For database connectors with manual mode set to true, after you hit the "Clear Table" widget, the subsequent fetch query fails.

Workaround: Toggle "Manually Configure Metadata" to false and then back to true.


Summary: Using literal values in the string.join function in a Flogo app fails both at design and run time.

Workaround: None.


Summary: In an Azure environment, repushing a Flogo app using the TIBCO CloudTM– Command Line Interface generates an error: “internal server error”.

Workaround: Repush the app in the User Interface. 


Summary: For un-deployed Flogo apps, updating engine variables from the Environment Controls section changes the  app status to Stopped in the App Details page.

Workaround: Update engine variables after the app is deployed.




Summary: If you save a flow in TIBCO Cloud Integration - Connect Flow Designer and the length exceeds the size of the Designer, sometimes the scroll bar does not allow you to scroll to the bottom of the flow. Workaround: Drag the blocks up higher or alternate hovering over the Query Block and the scroll bar until the scroll bar expands. 


Summary: In TIBCO Cloud Integration - Connect, occasionally when validating formulas in operation blocks the validation does not complete or generate an error. 

Workaround: Paste the formula directly from a text editor into the target field on the Fields tab to skip the formula validation process. 


Summary: In some cases a TIBCO Cloud Integration - Connect app configured with an agent cannot be accessed and a message displays indicating that you need to select an Agent. 

Workaround: Clear your browser case and remove cookies. 




Summary: A Kafka application connecting to a non Kerberos Kafka server must be supplemented with an empty krb5.conf file.

Workaround: None.



Summary: For the BusinessWorks™ Plug-in for Snowflake,  the following float values fail for the Query activity:

inf (infinity)

-inf (negative infinity)

Workaround: None.


Summary:  For the BusinessWorks™ Plug-in for Snowflake, sometimes an extra ActivityInput element with error indicator is loaded in the Input tab of the Query activity.

Workaround: Manually remove the unwanted ActivityInput element by right-clicking and deleting the selection.


Summary: For the BusinessWorks™ Plug-in for Snowflake the  Snowflake driver does not seem to support typecasting during batch operations. To work with different types of TIMESTAMP datatype (TIMESTAMP_NTZ, TIMESTAMP_LTZ, and TIMESTAMP_TZ) provided by Snowflake, we are typecasting the bind variable in SQL.

Workaround: When using TIMESTAMP fields do not use batch insert, set batchsize to 1.


Summary: For the BusinessWorks™ Plug-in for Snowflake, the Query activity fails when dealing with a NULL value from a NUMBER column.

Workaround: None.


Summary: Test connection hangs for users with multiple organizations because currently the AuditSafe plugin does not support multiple organizations.

Workaround: Select the organization used to test the connection. 



Summary: When a TIBCO Business Studio™ for BusinessWorks™ app is created with Excel functions and then deployed via the TIBCO Cloud™ – Command Line Interface using the bwadmin utility, the app fails to start. 

Workaround: None  



Summary: For the Flogo Connector for Data Conversion, when an existing copybook is modified, the changes are not automatically reflected in activities that use that copybook.

Workaround: You can refresh the studio page, navigate to a flow that uses the modified copybook and click every Parse, and Render activity that uses the copybook.


Summary: The MongoDB Insert document activity generates an incorrect output on failure, if the “Insert Many Documents” option is selected and the “Continue on Error” field is set to False.

 Workaround: None


Summary: MongoDB Trigger is not compatible with Cosmos DB.

Workaround: None


Summary: On the MongoDB Connection page, the value entered in the Key Password field is not validated when using SSL.

Workaround: None 


Summary: MongoDB activities time out in 30 seconds even if the Timeout value is set to a higher value.

Workaround: None



Summary : Content matcher is not working with integer type for TIBCO Cloud Messaging  Subscriber.

Workaround: None.


Summary:  For TIBCO Cloud™ Messaging, the subscriber stops receiving the message from the server after the reconnect attempts are exceeded.

Workaround: Make sure that the TIBCO Cloud™ Messaging  server is running normally and try the following: 

  • Restart the app.
  • Configure a larger number of AutoReconnectAttempts under the connection to make sure it can try to reconnect more times until the server is up.



Summary: The CDSServices PatientView palette activity fails when the workflow runs using TIBCO ActiveMatrix BusinessWorks Plug-in for HL7 with FHIR in TIBCO Cloud™ Integration.

Workaround: None.


Summary: Workflows created with TIBCO ActiveMatrix BusinessWorks Plug-in for HL7 with FHIR Version 8.0.0 FHIR activities are not compatible with Version 8.1.0.

Workaround: Update Version 8.0.0 workflows with Version 8.1.0 activities.


Summary: When running a CDSServices workflow with the ServiceDiscovery palette activity on TIBCO ActiveMatrix BusinessWorks Plug-in for HL7 with FHIR  in  TIBCO Cloud™ Integration, the associated URL must end in /cds-services/.

Workaround: Edit the URL to end with /. (Example: Change /cds-services to /cds-services/.)



Summary: PI JDBC activity returns the following error in the application startup in TIBCO BusinessWorks™ Container Edition and docker runtime: Directory separator should not appear in library name: lib/PINative.

Workaround: None



Summary: SmartMapper supplement is required even when the application uses SQL Server as the SmartMapper Storage Service.

Workaround: Before you push a SmartMapper application that is using SQL Server as the SmartMapper Storage Service, supplement a dummy smartmapper.zip with an empty folder.



Summary: For Avro activities, when app-level schemas are used, Avro schemas are not displayed in the list for selecting the schema. However, JSON schemas are wrongly displayed.Workaround: None



Summary: When using an alias that contains a space, an error is seen in the User Interface.

Workaround: When using an alias that contains a space, put it in double quotes or use an alias name without any spaces.


Summary:  In some cases,  you see an error stating "Column not found" even though your SQL statement is correct.

Workaround: Use an alias. For example, select cast('2002-01-01' as DATE) will give an error saying 'Column not found'. No error is generated if you use an alias as in select cast('2002-01-01' as DATE) as a1;


Summary: When using  the TIBCO Flogo Connector for Amazon DynamoDB, the DynamoDB Activity icons do not display consistently. If you exit the flow and open it again, you might see the PUT icon for Update/Delete operation.

Workaround:  None. 


Summary: For the TIBCO Flogo Connector for Amazon DynamoDB, when adding attributes manually for Put/update item, the first one or two attributes become blank and previously cached attributes are present in the attributes field.

Workaround: Clear both the blank attributes and previously cached attributes and add the attributes again.


Summary: The Iterator feature is currently not supported in TIBCO Flogo(R)  Connector for Jira.

Workaround: None


Summary: Attachments for TIBCO Flogo(R)  Connector for JIRA do not work.

Workaround: None


Summary: The connection dialog hangs if a non-existent host is used in the base URL for Magento.

Workaround: Refresh the page in your browser.


Summary: The SQLServer output schema is not available immediately to map in downstream activities.

Workaround: Click the SQLServer activity and come back to downstream activity. This time SQLServer comes up in the mappings.


Summary: When importing an older app, newly added fields such as Maximum Open Connections, Maximum Idle Connections, or Maximum Connection Lifetime are not available to configure.

Workaround: Create a new connection to use these new fields.


Summary: [MySQL]Bitwise is not supported.

Workaround: None.


Summary:  In the TIBCO Flogo Connector for Oracle Database, query parsing fails when a ROWNUM clause is present in the Select query.

Workaround: Use the Manually Configure Metadata option to correct the alias name in table schema.


Summary:  In the TIBCO Flogo Connector for Oracle Database, query parsing fails with a mismatch error when using a LIKE keyword for FLOAT and NUMBER data types.

Workaround: Use the Manually Configure Metadata option to correct the alias name in table schema.


Summary:  In the TIBCO Flogo Connector for Oracle Database, query parsing fails when the insert statement has a NULL value for NUMBER and DATE data type.

Workaround: Use the Manually Configure Metadata option to correct the alias name in table schema.


Summary:  In the TIBCO Flogo Connector for Oracle Database, when the alias used in a query contains a period (.), only a part of the name is displayed in the table schema.

Workaround: Use the Manually Configure Metadata option to correct the alias name in table schema.


Summary: In the TIBCO Flogo Connector for Oracle Database, query parsing fails when INSERT ALL is used.

Workaround: Use the Manually Configure Metadata option for configuring the metadata.


Summary: Metadata is not displayed under the ‘Table Schema’ field when connecting to an Oracle RDS database.

Workaround: None. 


Summary:  For the TIBCO Flogo® Connector for PostgreSQL, inserting multiple rows using different sets of parameters is not supported

Workaround: Use the output from an upstream activity to insert multiple rows.


Summary: User cannot use multiple user-defined aliases as a sub-string of other. The following query will not work:

select name, dept_name

from student

where student.dept_name=?dep



Workaround: None. 


Summary: For the TIBCO Flogo® Connector for Riak, the username is deleted from the Connection when importing an app.

Workaround: Update the Username with a value in the Connection after importing the app.


Summary: Connection failure when Riak Security is enabled with SSL.

Workaround: None.WISFPD-28

Summary: Create Prospects with custom fields is not supported.

Workaround: None. 


Summary: When using SAP S/4HANA Cloud connector, activities are not automatically assigned unique activity names when being added to a flow.

Workaround: Manually change the activity name after adding the activity to the

flow to make it unique.


Summary: When using the Flogo Connector for SAP S/4HANA Cloud, Input options in activities are missing after API service selection.

Workaround: None.


Summary: Authentication using OAuth does not work for TIBCO Flogo Connector for SAP Cloud for Customer.

Workaround: None


Summary: An application containing TIBCO Flogo for SAP SuccessFactors activities exported from Flogo Enterprise cannot be imported to TIBCO Cloud Integration.

Workaround: Configure TIBCO Flogo for SAP SuccessFactors activities directly in TIBCO Cloud for Integration.


Summary: For the TIBCO Flogo® Connector for SugarCRM, when importing an older flow, the Connection and Module fields for the  ReceiveSugarCRMessage trigger are not populated by default.

Workaround: Re-select the values for the Connection and Module fields from their respective drop-downs.


Summary: For the TIBCO Flogo®  Connector for Salesforce.com Einstein Analytics, you see token refresh errors for Flogo apps that use Salesforce-Wave activities if they run for a long duration of time.

Workaround: Reconfigure the Salesforce connection used in the activities and then push the app again. 


Summary: Entering invalid connection details for the  TIBCO Flogo Connector  for Snowflake, including an invalid warehouse, database, or schema name, does not generate an error. 

Workaround: None


Summary: Configuring a flow for Snowflake that contains an Insert with multiple rows of data generates an error at design-time, but executes successfully at runtime. 

Workaround: None


Summary: When using the TIBCO Flogo Connector  for Snowflake in TIBCO Cloud Integration, the connector cannot connect to Snowflake with the OAuth authentication type.

Workaround: None.  


Summary: Solr connection icons created for older apps do not load up properly. But there is no impact in the runtime functionality of the applications using the connection.

Workaround: None


Summary: A design time error displays when there is no value for count and interval fields under Retry on the Error tab.

Workaround: Set count and interval field value back to default value 0 or set any value you expect, but do not leave the values blank.


Summary: Applications with Zoho connections created in 1.0.1 or earlier versions do not work when you import them in the version 1.1.0.

Workaround: After importing applications, create a new connection on 1.1.0 and use that connection in the application.