Develop / TIBCO Flogo® Connectors Known Issues

To access release notes see: TIBCO Cloud? Integration Release Notes at https://community.tibco.com/s/article/TIBCO-Cloud-Integration-Release-Notes.

To access Known Issues for other TIBCO Cloud ? Integration capabilities see TIBCO Cloud ? Integration Known Issues at https://community.tibco.com/s/article/tibco-cloud-tm-integration-current-known-issues

TIBCO Flogo® Connector for Amazon DynamoDB

WIDYDB-124

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

Workaround:  None. 

WIDYDB-130

Summary: For the TIBCO Flogo Connector for Amazon DynamoDB, when adding attributes manually for the 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.
 

TIBCO Flogo® Connector for Amazon Elastic File System

WIAMEF-30

Summary: AWS Connections using Session Tokens are not working for the Amazon Elastic System.

Workaround: None.
 

TIBCO Flogo® Connector for Amazon Glacier

WIAMGL-26

Summary: AWS Connections using Session Tokens are not working for Amazon Glacier.

Workaround: None.

TIBCO Flogo® Connector for Amazon Kinesis

FGAZKS-54

Summary: The tags object should be supported for Create DataStream Activity that is Firehose Stream Type.

Workaround: None.
 

FGAZKS-69

Summary: When trying to Create Firehose-Delivery Stream, using the CREATE activity results in an error at runtime.

Workaround: None.
 

TIBCO Flogo® Connector for Apache Avro

WIAVRO-65

Summary: 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
 

TIBCO Flogo® Connector for Apache Kafka

FGKAFKA-98

Summary: If the server certificate is not configured, by default the "InsecureSkipVerify" flag is set as true in the tls configuration.

Workaround: None.
 

TIBCO Flogo® Connector for Apache Pulsar

FGPUL-365

Summary: When you override Broker CA for OAuth2 Authentication, an error is displayed.

Workaround: None.

FGPUL-241

Summary: When the Apache Pulsar Producer Activity is present in a running app, topics are created when the activity executes and a message is published, not when the app starts.

Workaround: None.

FGPUL-267

Summary: When running an app as an Apache Pulsar function, the function does not work if there are multiple input topics.

Workaround: None.
 

TIBCO Flogo® Connector for Apache Solr

WISOLR-39

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
 

TIBCO Flogo® Connector for Data Conversion

FGDCNV-78

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

TIBCO Flogo® Connector for GitHub

WIGTHB-17

Summary: You cannot build an app executable if your app uses the TIBCO Flogo® Connector for GitHub.

Workaround: None.
 

TIBCO Flogo® Connector for Google Cloud Pub/Sub

FGGCPS-42

Summary: On the Windows operating system, installing the connector and generating the binary and docker images takes a long time.

Workaround: None

FGGCPS-40

Summary: In the Message Publisher Activity, when a user keeps the topic id blank in the settings tab and overrides from the input tab, an error is displayed in UI logs.

Workaround: None
 

TIBCO Flogo® Connector for Google Cloud SQL

WIGSQL-57

Summary: For the PostgreSQL database, during design-time, the Create function is not permitted in the GoogleCloudSqlQuery Activity.

Workaround: None

WIGSQL-58

Summary: For the PostgreSQL database, during design-time, parameters do not load into the table schema for function calls.

Workaround: None

WIGSQL-59

Summary: For the PostgreSQL database, during design-time, the COALESCE() function does not work when used with the Select statement.

Workaround: None

WIGSQL-60

Summary: For the PostgreSQL database, during design-time, a query, such as "Select 1", generates an error.

Example: Select 1 from table_name;

Workaround: None

WIGSQL-61

Summary: For the PostgreSQL database, during design-time, the table schema is not loaded for queries that involve grouping sets and cube.

Workaround: None

WIGSQL-62

Summary: For the PostgreSQL database, during design-time, an error occurs for XML and JSON data types.

Workaround: None

WIGSQL-105

Summary: After the February 2022 release of TIBCO Cloud Integration, if you push a new or re-push an existing Flogo app that uses TIBCO Flogo® Connector for Google Cloud SQL then the app does not work.

Workaround: None

WIGSQL-130
Summary: Design time error for BIT datatype in Google Cloud SQL.
Workaround: None. 

TIBCO Flogo® Connector for Google Cloud Storage

WIGSQL-105
Summary: For TCI 3.3.1 or higher, if you push a new Flogo application or re-push an existing Flogo application which uses TIBCO Flogo® Connector for Google Cloud SQL, the application does not work.
Workaround: None. 
 

TIBCO Flogo® Connector for Greenplum Database

*WIGPLM-118

Summary: When trying to connect to the Greenplum database at design time using the TIBCO Flogo® Connector for Greenplum Database, an ODBC driver error is generated.

Workaround: None. 
 

TIBCO Flogo® Connector for HTTP

FGHTTP-89

Summary: Response is received as Null when a request of type Multipart/form-data or application/x-www-form-urlencoded is made from the HTTP service in Data mode.

Workaround: Use processing mode as Proxy instead of Data for making such a request.
 

TIBCO Flogo® Connector for IBM MQ

FGIBMQ-58

Summary: Flogo IBM-MQ GMO functionality is unstable for the Get activity.

Workaround: None. 

FGIBMQ-59

Summary: The MQ Get activity is checking and receiving the first message in the queue even though it exceeds the Max Messages size if the next message is under the Max Message Size. An error similar to the following should be generated: 

The messages that are larger than the buffer size are truncated.

Workaround: None.

FGIBMQ-61

Summary: Unable to run the MQ Subscriber activity with Durable Subscription configured. 

Workaround: None. 

FGIBMQ-62

Summary: The ?retain Message? functionality for the MQ Publish activity is not working.

Workaround: None. 

FGIBMQ-67

Summary: The Flogo Connector for IBM MQ is not supported on the Microsoft Azure region.

Workaround: None. 

TIBCO Flogo® Connector for Jira

WIJIRA-46

Summary: Attachments for TIBCO Flogo®  Connector for Jira do not work.

Workaround: None.

WIJIRA-48

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

Workaround: None

TIBCO Flogo® Connector for Magento

WIMGTO-110

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.
 

TIBCO Flogo® Connector for Marketo

FGMKTO-80

Summary: Error handler is not triggered in cases where the configuration has no data added in the input mapper.

Workaround: None

FGMKTO-81

Summary: When a user imports an app JSON created prior to the February 2022 release, the Marketo Connection disappears from the connection field.

Workaround: Upgrade the Marketo connector to the latest version.

TIBCO Flogo® Connector for Microsoft Azure Service Bus

WIAZSB-321

Summary: If you try to update any configuration on the Azure portal for topic in ReceiveAndDelete mode, it stops consuming messages.

Workaround: None.
 

TIBCO Flogo® Connector for Microsoft Azure Storage

WIAZSG-197

Summary: Existing validation issues on an App are not resolved by upgrading Azure storage contribution.

Workaround: Exporting the app and importing it again with the same environment resolves the issue.

TIBCO Flogo® Connector for Microsoft Dataverse

FGMSDV-120
Summary: There is no option for the Microsoft Dataverse connector to be promoted to the org level. We can see only the Reset Metadata option.
Workaround: None.

FGMSDV-111
Summary: There is no validation error message displayed if no connection is selected in any Microsoft Dataverse activity.
Workaround: Manually select the connection and click the Validate button.

FGMSDV-110
Summary: If an app has Microsoft Dataverse activities, it takes a long time for them  to execute in the flow tester.
Workaround: None.

FGMSDV-108
Summary: An app with Microsoft Dataverse connections takes over 1 minute to get imported.
Workaround: None.

FGMSDV-89
Summary: Initially a list of objects takes a long time to load when the user selects a connection and then an object.
Workaround: None.

FGMSDV-88
Summary: Fetching metadata initially takes a  long time.
Workaround: None.

FGMSDV-65
Summary: In the Update activity, if the user enters values in the fields that do not exist in the  tables, then an incomplete error message is displayed.
Workaround: None.

FGMSDV-64
Summary: When we import an app, the UCS Microsoft Dataverse Connection is not displayed in the list of connections in activities.
Workaround: Manually open the activity and select a connection (if it exists) or create a new connection and select it.

FGMSDV-58
Summary: The Flogo app binary having a Microsoft  Dataverse connector does not run.
Workaround: None.

FGMSDV-42
Summary: On the Connections page, even if a Microsoft Dataverse connection is used in an app, the Usage count is always displayed as 0.
Workaround: None.

TIBCO Flogo® Connector for Microsoft OneDrive

WI1DRV-17

Summary: The current OAuth implementation for the TIBCO Flogo Connector for OneDrive connection generates an Access Token that expires after 60 minutes and does not create any Refresh Tokens. After 60 minutes any activity generates an "Access Token Expired" error during runtime.

Workaround: If any app generates the "Access Token Expired" error message, then you can regenerate a secret Id of the back-end azure app through the portal, and use the newly generated secret value to log in to the same connection again.
 

TIBCO Flogo® Connector for Microsoft SQL Server

WIMSSS-92 

Summary: For Microsoft SQL Server, the OUTPUT clause in INSERT INTO is not supported. For example, the following INSERT INTO statement does not return the expected value for promotion id:

INSERT INTO promotions (

    promotion_name,

    discount,

    start_date,

    expired_date

) OUTPUT inserted.promotion_id

VALUES

    (

        '2018 Fall Promotion',

        0.15,

        '20181001',

        '20181101'

    );

Workaround: None

WIMSSS-213

Summary: For Microsoft SQL Server, after importing a Flogo app that was exported previously, an error is shown on the activities even after establishing a connection.

Workaround: Refresh the page or click on the respective activity again.

WIMSSS-310

Summary: At design time, when an incorrect query is entered for Insert, Delete, or Update activities, no error message is displayed.

Workaround: None

WIMSSS-327

Summary: When passing a list of values in the prepared parameter, the query does not return any values.

Workaround: Pass multiple prepared parameters like ?a1,?a2.

*WIMSSS-355

Summary: In case of queries combining results from multiple tables, if the tables have identical column names, then the repeated column names are renamed as columnName_<number>.

WIMSSS-443

Summary: For Azure SQL Server Validate Server Certificate, set as True is failing.

Workaround: Enable On-Premise Database.

WIMSSS-444

Summary: For Azure-SQLServer, once the binary is executed and Ctrl-C is used to exit, unexpected logs are being printed.

Workaround: None.

WIMSSS-508 

Summary: There is no support for HIRARECHYID, GEOGRAPHY, and GEOMETRY data types in SQL Server activities currently. 

Workaround: None. 
 

TIBCO Flogo® Connector for MongoDB

FGMGDB-83

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

FGMGDB-93

Summary: MongoDB Trigger is not compatible with Cosmos DB.

Workaround: None

FGMGDB-96

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

Workaround: None 

FGMGDB-107

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

Workaround: None

FGMGDB-117

Summary: options such as update, find, and delete do not work when the auto generated '_id' is given in the input criteria.

Workaround: With user given ids in the documents, MongoDB activities work. While inserting a document, specify a unique id in the input JSON.
 

TIBCO Flogo® Connector for MQTT

WIMQTT-105 / FLOGO-4136

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

Workaround: None

TIBCO Flogo® Connector for OData

FGOD-50

Summary: The output of the content-length response header of OData Query activity is not getting mapped to the Log Message activity.

Workaround: None

TIBCO Flogo® Connector for Oracle Database

WIORA-79

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

WIORA-84 
Summary: Unable to build application binaries for Windows/amd64, Darwin/amd64, and Linux/x86 platforms.
Workaround: None

WIORA-153

Summary: If the password contains a colon (:), an error occurs while connecting to the database.

Workaround: None.

WIORA-242

Summary: You cannot see new GUI changes that were added to support the connection to Oracle Database using Service Name in the existing Oracle Database connection when the contribution is upgraded from TIBCO Flogo® Connector for Oracle Database 1.0.1 to TIBCO Flogo® Connector for Oracle Database 1.0.1 HF-001.

Workaround: Create a new Oracle Database connection and use it in the Oracle Database activities.
WIORA-286

Summary: Apps using the Connector for Oracle DB fail to execute from the Flow Tester. 

Workaround: None.

WIORA-322 
Summary: Unable to fetch the query when a non default schema is used in Oracle Database activity.
Workaround: Enter the schema name manually in the query. 
For example, 
select * from schemaName.tableName; 
 

TIBCO Flogo® Connector for Oracle MySQL

WIMYSQ-440

Summary: If there is no SSL server and you configure the connection as an SSL Connection with the TLS Required option selected, no error is generated at design time, only at run time. 

Workaround: None. 

WIMYSQ-464

Summary: At design time, when an incorrect query is entered for Insert, Delete, or Update activities, no error message is displayed.

Workaround: None.

WIMYSQ-488

Summary: When importing app JSON files with MySQL, SQL Server and PostgreSQL activities, an error marker comes up on the activities even after updating the credentials.

Workaround: Refresh the page or click on the respective activity again.

*WIMYSQ-524

Summary: In case of queries combining results from multiple tables, if the tables have identical column names, then the repeated column names are renamed as columnName_<number>.

Workaround: For Duplicate column names use an alias. 
 

TIBCO Flogo® Connector for PostgreSQL

WIPGRS-88

Summary: When using a time data type, "time without timezone" is not supported.

Workaround: None

WIPGRS-327

Summary: After importing a Flogo app that was exported previously,  an error is shown on the activities even after establishing a connection.

Workaround: Refresh the page or click on the respective activity again.

*WIPGRS-387

Summary: When configuring the connection for SSL Mode, the Client-key and Client-certificate are not validated at design time.  If either one is invalid, an error is generated at run time. 

Workaround: None. 

WIPGRS-429

Summary: In PostgreSQL "rowsAffected" is not showing in the output schema of the INSERT and UPDATE activity.

Workaround: None

*WIPGRS-460

Summary: In case of queries combining results from multiple tables, if the tables have identical column names, then the repeated column names are renamed as columnName_<number>.

Workaround: For duplicate column names use an alias.

WIPGRS-538

Summary: When Nullable fields are left empty, an error is generated.

Workaround: Remove any fields that are not required from the query to automatically treat those fields as NULL.

WIPGRS-606

Summary: When you select any schema other than "public" and type in the query, an error message, "<table_name> doesn't exist", is displayed.

Workaround:Type the <schema_name> <table_name> without using the SQL editor.

TIBCO Flogo® Connector for Redis

WIRDIS-135

Summary: When you upgrade the Redis application, only the old lists of commands are shown in the UI and the new commands are missing.

Workaround: To get the new command lists in the UI, go to the connection and save it.

WIRDIS-136

Summary: When you import any Redis application, it takes the existing Redis connection even though the mentioned connection name is different.

Workaround: None

WIRDIS-137

Summary: For the ZINCRBY Redis command, the output shows as an integer instead of a string. When the INCR option is specified for the ZADD Redis command, it fails to return the expected value as Bulk string reply.

Workaround: None
 

TIBCO Flogo® Connector for Riak KV

*WIRIAK-36

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

WIRIAK-37

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

Workaround: None.

TIBCO Flogo® Connector for Salesforce Pardot

*WISFPD-28

Summary: Create Prospects with custom fields is not supported.

Workaround: None. 
 

TIBCO Flogo® Connector for Salesforce.com Einstein Analytics

WISFEI-43

Summary: If no inputs are provided in the record, then the wave connector generates the following error: "interface conversion: interface {} is nil, not map[string]interface {}exception."

Work Around: None

WISFEI-62

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

TIBCO Flogo® Connector for SAP Cloud for Customer

WISAHY-24

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

Workaround: None
 

TIBCO Flogo® Connector for SAP HANA Database

WISAHC-16

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.

TIBCO Flogo® Connector for SAP Solutions

WISAP-60

Summary: When building a binary executable for TIBCO Flogo® Connector for SAP Solutions on Windows amd64, Linux x86, or Darwin amd64, the build fails with a "Build executable error”.

Workaround: None.

TIBCO Flogo® Connector for SAP SuccessFactors

WISASF-35

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.
 

TIBCO Flogo® Connector for Slack

*WISLCK-92

Summary: If you import an old app that references the channels API object, an error is generated.  This object has been deprecated by Slack. 

Workaround: Update the app to perform channels' object operations by using the Conversations object.

*WISLCK-93

Summary: The channels API object disappears from the drop-down list after testing an app and reopening the flow.  This object has been deprecated by Slack. 

Workaround: Update the app to perform channels' object operations by using the Conversations object.
 

TIBCO Flogo® Connector for Stripe

*WISTRP-230 

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.
 

TIBCO Flogo® Connector for SugarCRM 

WISCRM-187

Summary: During design time, if you select the Lead, User, or opportunities module in the Settings tab for the create activity, the Input tab displays a blank screen. 

Workaround: None
 

TIBCO Flogo® Connector for TIBCO Cloud? Messaging

FGTCM-18

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

Workaround: None.

FGTCM-53

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

FGTCM-62 / FLOGO-4936

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

Workaround: None.
 

TIBCO Flogo® Connector for TIBCO® Data Virtualization

FGTDV-45

Summary: The delay between retry attempts is more than 2 minutes when the TDV server is unreachable, not honoring connection timeout.

Workaround: None.

FGTDV-46

Summary: With Retry On Error before all retry attempts are completed, if we start the TDV server then the app does not auto connect.

Workaround: None.

FGTDV-136

Summary: When you set up a connection from Flogo to TIBCO Data Virtualization on a cloud instance without using the tibagent, a ?Connection failed? error is displayed.

Workaround: Enable dbservice and set on-prem to true.

FGTDV-150
Summary: Some letters (a, c, g, k, m, p, and t) in the auto suggestion list do not indicate anything.
Workaround: None.

FGTDV-151
Summary: Tables are not auto-populated (if you use Ctrl + space) when you open an app after sometime.
Workaround: Go to the Settings tab, change the catalog and switch it back. You can see the tables being auto populated.

TIBCO Flogo® Connector for TIBCO Enterprise Message Service?

FGEMS-34
Summary: Durable topic subscribers are not supported.
Workaround: None. 

FGEMS-27 
Summary: The SSL handshake logs are shown on the application startup unexpectedly.
Workaround: None. 
 

TIBCO Flogo® Connector for Twilio

FGTWLO-90

Summary: Sign-in prompt is generated for expired Twilio auth token in connection.

Workaround: Use a valid auth token in the connection tab.
 

TIBCO Flogo® Connector for WebSockets

*FGWSKT-62

Summary: On the Endpoints tab, if you copy the Endpoint URL of the application containing the Websocket Server trigger, by default the URL has https:// instead of wss://.

Workaround: To connect to the Websocket Server trigger from a Websocket client, in the URL, change https:// to wss://.

FGWSKT-112

Summary: When a Flogo Websocket server instance is stopped, the following error is generated on the Websocket Subscriber trigger:

error is: websocket: bad handshake

response code is: 404, payload is: Resource was not found

Workaround: None
 

TIBCO Flogo® Connector for Zoho CRM

*WIZOHO-97

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

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

TIBCO DB Services

*WIDBSV-148

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.

*WIDBSV-347

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;

*WIDBSV-427

Summary: Table names containing spaces generate design time errors similar to the following: 

"SQLNumResultsCols: {6000} [tibcosoftwareinc][ODBC 20101 driver][Microsoft SQL Server]Incorrect syntax near 'Order Details'.{6000}[tibcosoftwareinc][ODBC 20101 driver][Microsoft SQL Server]The batch could not be analyzed because of compile errors.".

Workaround: Enclose the table name in square brackets, for example: select * from [Order Details]

WIDBSV-451

Summary: In a select query with a where clause, if the parameter name is the same as the column name, the return type is incorrect.

Workaround: None.

WIDBSV-509
Summary: For incorrect query,an error message is not showing up in the Insert, Delete and Update activities at design time.
Workaround: None.