TIBCO Scribe® Online Current Known Issues
General
Agent
SCCORE-7902
Summary: If an Agent is off the ServiceBus when a new ServiceBus is added and is instructed to connect to that new Service bus, the Agent fails to connect with the following error: (Case # 02090507)
Cannot find a namespace that matches {0}.
Workaround: Restart the Agent.
SCCORE-7673
Summary: When installing an On-Premise Agent, extended ASCII characters are not supported in the path for the installation directory, and cause the Agent installation to fail. For example, C:\ScribeüД 电脑 is not supported, but C:\ScribeAgent is supported.
Workaround: Use the default installation directory or create a directory that does not include extended ASCII characters in the name.
SCCORE-752
Summary: The URL the On-Premise Agent uses to connect to the Cloud contains a trailing period (.), such as https://agent.scribesoft.com.. Some firewalls do not permit the trailing period (.), which causes the Agent to stop running. (Case # 01788305)
Workaround:
- Navigate to the TIBCO Scribe® Online Agent folder. The default location is ..\Program Files [(x86)]\Scribe Software\TIBCO Scribe® Online Agent\.
- Use a text editor, such as Notepad, to open the Scribe.Core.ProcessorService.exe.config file.
Note: Make sure to run the text editor as Administrator or the changes to the file may not be saved.
- Locate <add key="AdjustedURL" value="true" /> and make sure that the value = true. This prevents your changes from being overwritten when you restart the Agent. If this entry does not exist. Add it to the add key section just before <add key="AgentApiUrl" value="https://agent.scribesoft.com." />.
- Locate <add key="AgentApiUrl" value="https://agent.scribesoft.com." /> and remove the period after scribesoft.com.
- Restart the Agent Windows service.
Blocks
SCCORE-5688
Summary: The Wait for Request Block does not accept null values for fields that are data type Boolean or Datetime. (Case # 01920876)
Workaround: Use only string data types for all fields in the Request tab of the Wait for Request Block.
67432 / SCCORE-2336 / SCCORE-3411
Summary: If a Fetch Block filter value contains a double slash (//), the slashes and any characters that follow them are dropped when sending the filter value. For example, if the value is "https://google.com", only "https:" is used in the filter. (Case # 01845726)
Workaround: Use a formula with the CONCATENATE function to concatenate the sections. Example: CONCATENATE("https:", $"//", "api.scribesoft.com:443/v1/orgs")
SCCORE-1520
Summary: Decimal type fields displayed in the Query Block Preview tab display only the first two digits after the decimal, however, all digits are sent to the target. (Case # 58233, 01718730)
Workaround: None.
SCCORE-1342
Summary: The BuildWith Block Fields tab does not indicate which fields are required and the 
icon says Required=No for all fields.
Workaround: Check the Errors and Warnings tab for information on required fields.
SCCORE-1333
Summary: Operation results for the REST Connector Post operation are available in subsequent Blocks but do not display when using the Formula Editor or filter fields. (Case # 01767940)
Workaround: Manually type the reference to the results field.
SCCORE-1027
Summary: If a Map contains Lookup Blocks with caching enabled and those Blocks are accessing data from multiple SQL schemas where there is more than one record with the same lookup criteria, errors similar to the following are generated: (Case # 01792849)
Message: An item with the same key has already been added.: Error in calling Operation Query (Lookup Block)
Workaround: Disable caching or use the default schema.
SCCORE-936
Summary: Source field names that contain spaces or special characters display in the User Interface with the spaces or characters removed. For example Contact Address 1 displays as ContactAddress1, with no spaces. If you have field names that become similar or the same when special characters or spaces are removed and you select those fields in a Lookup Block, the Connector returns null values. For example, having fields named Total Tax Rate and Total Tax may cause an issue. (Case # 01784872)
Workaround: If possible, rename the fields in the source datastore. In some cases exporting and reimporting the Map resolved the problem.
74993 / SCCORE-1763
Summary: If you use a LOOKUP field, such as LOOKUPTARGETVALUE, as part of a formula in a target Block, an error displays indicating that you should use Lookup Blocks in Maps. When all other errors for the Map are corrected, this same Lookup error displays for all Blocks in the Map.
Workaround: None.
74839 / SCCORE-1765
Summary: When metadata is reset, if labels for hierarchical Relationships displayed on the Block Properties Include tab have changed, the old label is removed but the new label does not display preventing you from remapping the relationship.
Workaround: Configure a new Block of the same type and remove the old Block or disable the relationship higher in the tree and then reenable it to see the new relationship name when the branch is expanded.
70531 / 71887 / SCCORE-1540
Summary: When property names contain periods (.), the period is stripped away in Query filters. Only the information after the last period is included in child entity names displayed on the Query Include tab. Deleting the filter field containing a period in the name after a preview does not remove the filter from the Query. (Case # 66685, 68292, 67062, 01726811, 01728413, 01727188)
Workaround: None.
69057 / SCCORE-1541
Summary: If your system date falls on the last day of the month, such as the 31st, and you are modifying the Net Change date in a Query Block to a date within a month that has fewer days than the current month, when you save the Block Properties the Net Change date is advanced by one month. For example, if today is July 31st, and you are setting the Net Change date to May 25th, when you save the Block the date is saved as June 25th. (Case # 66937, 01727063)
Workaround: Change the system date on your computer to be a date that is not the last day of the month. Modify the Net Change date and save the Block and Map. Once the Net Change date is set correctly, change the system date on your computer to the correct date.
66610 / SCCORE-1535
Summary: Validation on the Formula Editor does not detect when a field of type list array is used in a formula that attempts to convert the data to a double. That conversion is not supported and the problem is not caught until there is a record error when attempting to run the Solution. (Case # 64744, 01724899)
Workaround: None.
45025
Summary: The Block Properties Include Tab for the CreateWith Block sometimes shows duplicate complex property names.
Workaround: Close the CreateWith Block Properties dialog and open it again.
44963 / SCCORE-1521
Summary: The Query Block Preview tab does not work if the filter value on the Filter tab contains the LOOKUPTABLEVALUE2 function. The Map runs correctly, only Preview is affected. (Case # 59046, 62370, 01722641, 01719477)
Workaround: None.
44365
Summary: After the initial configuration, the Query Block Preview tab does not include the Child record count for hierarchical data when relationships are selected on the Include tab.
Workaround: None.
42949
Summary: Unicode characters, such as Cyrillic, are not supported for the Block Rename feature accessed via the Gear menu on the selected Block.
Workaround: None.
41401 / SCCORE-2844
Summary: Underscores are not supported for the Block Rename feature accessed via the Gear menu on the selected Block.
Workaround: None.
Connections
SCCORE-8624
Summary: Deleting a Map from a Solution may leave a record of the Connections for that Map in the database. This prevents the associated Connections from being deleted because they appear to be in use. (Case # 02124141)
Workaround: Contact Support for help deleting your connections.
SCCORE-8294
Summary: If an OAS specification used with the REST Web Services Connector has a Query Parameter field name containing square brackets [ ], TIBCO Scribe® Online treats the brackets as special characters and removes them. When attempting to use the Query Parameter with the brackets in the field name in a request, the request fails with an error similar to the following: (Case # 02098907)
ERROR: Exception Type : RestConnectorException
Message : Exception executing method: RESTConnector.ExecuteQuery| Status: BadRequest Bad Request |
Content: {"message":"\"%fieldName\" is required. Enter and try again.","parameters":{"fieldName":"searchCriteria"}}| Message: Bad Request
Workaround: None.
SCCORE-6883
Summary: If you modify a Connection used in a Map and run the Map immediately, it uses the original Connection settings instead of the new settings. (Case # 02038977)
Workaround: Wait a few minutes after modifying the Connection to run the Map. This gives the system time to synchronize the new Connection information with the Agent associated with the Map.
48429
Summary: Reassigning Connections from within a Map does not always update the Solution Edit page immediately.
Workaround: Navigate to another page, then return to the Solution Edit page.
Debug
SCCORE-7428
Summary: The Map Debug process fails if Non-printable ASCII characters are returned from source data. (Case # 01931525, 01941061, 01941597, 01952448)
Workaround: The Map runs correctly when not in Debug mode.
SCCORE-6449
Summary: In a Map, if the Debug process reaches a Continue block set to "Continue to Next Child Record", the process remains in progress indefinitely and generates an error similar to the following: (Case # 01941136)
An error was encountered processing this request
Workaround: Restart the agent and run the map normally, not in Debug mode.
SCCORE-1465
Summary: If a Map uses the GETDATETIME() and GETUTCDATETIME() functions and you run that Map in Debug mode, the datetime information displayed is always the UTC datetime. However, the correct datetime values are being used. This is a Debug User Interface issue. (Case # 01806275)
Workaround: Verify the data being sent using the Agent logs or by looking in the target datastore.
48190
Summary: Setting Conditional Breakpoints on a For Each Child Block causes Debug to fail with an error similar to the following:
Object reference not set to an instance of an object.
Workaround: None.
38225
Summary: When running a Map in Debug, Match Criteria sometimes does not display on the Data tab in the Lookup.formula field. If you have more than one Match field, they all display.
Workaround: None. The Map does execute correctly at runtime.
37628
Summary: In Debug Mode, when setting Conditional Breakpoints for a Fetch Block, child fields are not displayed.
Workaround: None.
Execution History
SCCORE-8433
Summary: The Export All option on the Execution History Details for a Replication Solution fails with an error similar to the following: The data is invalid"
Workaround: None. The Export All option should not be enabled for Replication Solutions.
74581 / SCCORE-1546
Summary: Reprocessing failed source data records with child records in the thousands can cause the View Error Details screen to fail. (Case # 69896, 01771388, 01729809, 01794012)
Workaround: Use the API to retrieve error details for failed records.
69004
Summary: Selecting Reprocess All for a Solution Execution with errors only reprocesses those records that have been synchronized to the TIBCO Scribe® Cloud.
Workaround: Wait until the numbers in the Pending and Failed columns on the Execution History page are the same. That indicates that the records are available for reprocessing.
41043
Summary: On the Solution Edit page, when you select Run, the Solution starts and the Status displays in the top right corner. The duration associated with the In Progress status is affected by the difference between the Agent server time and the local PC time. For example, if the PC time is 2 minutes ahead of the Agent server time and a Solution starts, the duration associated with the In Progress status immediately goes to 2 minutes.
This can be confusing because the duration, as the Solution executes, continues to be inflated. When you view the Execution History after the Solution completes, the duration there would be 2 minutes less than the duration displayed in the Solution Edit Status field.
Workaround: None.
38550
Summary: Execution History Details can be selected for executions that have ended in a Fatal Error and have no Details records.
Workaround: None.
36800
Summary: Record Errors in Execution History Details do not always display the value for a source field if width of the value exceeds the display area.
Workaround: None.
Formula Editor
SCCORE-2426
Summary: The CSVLOOKUPVALUE function returns incorrect data if the cache size is smaller than the lookup file size. In addition, the lookup file should contain no more than 10 columns. (Case # 1809287)
Workaround: Modify any formulas using the CSVLOOKUPVALUE function to ensure that the cache size is large enough.
SCCORE-1012
Summary: The CLEAN function removes some Cyrillic characters that are below Hex 32, such as the H character in this example: CLEAN("г.Новосибирск"). (Case # 01794715)
Workaround: Try the REPLACEREGEX function instead.
41936
Summary: Highlighting text in a formula and selecting a function from the function list does not wrap the selected text in parentheses associated with the selected function causing the formula to be incorrect.
Workaround: Add functions manually by typing them into the correct location in the formula.
Lookup Tables
-
Maps
SCCORE-8729
Summary: When an inbound message is parsed by a Request/Reply map, UTC datetimes that are datatype string are sometimes converted to datatype datetime, which reformats the data. For example, String field: 2022-09-21T09:21:15Z is converted to 9/21/2022 9:21:15 AM. (Case # 02134217)
Workaround: Use the TOSTRING() function to ensure that the field remains a string on the target datastore.
SCCORE-6947
Summary: Deleting a Map in an Event Solution that has outstanding messages, causes the message queue to be blocked and no messages are processed. (Case # 02041258, 02044203)
Workaround: Contact support to help you clear the message queue for the deleted Map.
SCCORE-6512
Summary: When processing a large volume of inbound messages in a Message Map, connections are not closed in a timely manner consuming memory, which can cause processing to slow down. (Case # 01939306, 01941271, 01941069, 01944145 )
Workaround: Restart the agent.
SCCORE-4859
Summary: When deleting a large number of Maps from a Solution, there may be a delay updating the user interface causing deleted Maps to continue to display. (Case # 01890333)
Workaround: None.
69215 / SCCORE-1581
Summary: Duplicating an Event Map automatically sets it to Enabled but does not generate the endpoint URL for that Map.
Workaround: Instead of duplicating the Map, export the original Map and import it into the appropriate Solution. Open the imported Map to generate the endpoint URL.
68466
Summary: No Map revision is generated if the only change to the Map was to add a comment.
Workaround: Make some other minor change to the Map along with the Comment to generate a new revision.
65766 / SCCORE - 3051
Summary: If you import a Map, open it, select Validate, and then select Apply, the Map status is not changed to Complete / Enabled.
Workaround: Select OK instead of Apply.
SCCORE-151 / SCCORE-1526
Summary: In some cases the Agent attempts to run a Solution before the Agent has completely synchronized with the TIBCO Scribe® Cloud, generating errors similar to the following: (Case #01723084, 01715953, 01717103, 01719464, 01719506, 01722779, 01723303, 01723542, 01723970)
Fatal Error (Process Definition 3e55290f-175c-4de0-a1bb-1def540329df) is not currently on this Agent.
Workaround: This is a timing issue where it appears that the Solution or Map can be run immediately when the Agent is not actually ready. It is a rare occurrence. If you see this error message, disable the Solution, wait a few minutes and enable the Solution again. Wait a few minutes to give the Agent time to synchronize with the TIBCO Scribe® Cloud. Another option is to export the Maps from the Solution with the errors and import them into a new Solution.
56697 / SCCORE-1837
Summary: Manually running a Map validates all Connections in all Maps in the associated Solution. If there is a broken Connection in another Map, the selected Map fails with an error.
Workaround: Export the Map you want to run and import it into a separate Solution for testing. You do need to resolve the broken Connection before running the Solution.
41860
Summary: Reassigning a Connection generates “entity is undefined” errors when the entity name in the original Connection and the new Connection are not the same case, such as account and Account.
Workaround: Open the affected Blocks and select the correct entity for the new Connection.
37417
Summary: Selecting the Edit link for the datetime under Most Recent Record Processed on the Query Block Properties Net Change tab sometimes generates an “Invalid Date” error message, even though the date has not yet been set.
Workaround: None.
37418
Summary: When attempting to manually modify the datetime on the Query Block Properties Net Change tab under Most Recent Record Processed for a Map that has never been run, you cannot type in the date field.
Workaround: You must use the Calendar icon to select the date, and then you can manually enter the time.
36786
Summary: If the Errors and Warnings tab on the Map editor contains more than one page of errors and warnings, only those displayed in the list on the Properties tab are reflected by the error and warning icons on the Map Blocks.
Workaround: If you scroll through the pages of errors the Blocks update based on what is displayed. As you resolve the errors the list becomes shorter and the remaining errors eventually display.
36782
Summary: If the Errors and Warnings tab on the Map workspace contains more than one page of errors, selecting an error to display the Block properties for the associated Block and then immediately canceling sometimes causes the page navigation at the bottom of the tab to disappear.
Workaround: Select the Validation button at the bottom of the Map workspace.
35198
Summary: When configuring a new Connection through the Map workspace using the Create New Connection link on the Add Connection dialog, the list of Connectors available does not honor the type of Agent assigned to the Solution. For example, the Connector for Microsoft Dynamics GP does not support Cloud Services, but is displayed in this list even if a Cloud Service is assigned to the Solution.
Workaround: Verify that the Connection supports the Cloud Service before adding it to a Solution that uses the Cloud Service.
31891
Summary: When TIBCO Scribe® Online is retrieving metadata for a Connection in a Map, there is no message if the request times out.
Workaround: Save the Map and try again. Check your Agent status to make sure the Agent is running. Make sure credentials in the Connection dialog for that Connection are correct.
Marketplace
35246
Summary: If you install a Connector in an Organization with no Agents installed, the green status icon disappears for installed Connectors on the Marketplace page.
Workaround: Install an On-Premise Agent or provision a Cloud Service and then install the Connector from the Marketplace.
Notifications
SCCORE-2601
Summary: In some cases, when an email message is generated but fails to send, future emails from TIBCO Scribe® Online are blocked. (Case # 01815925, 01815989, 01816300, 01816310, 01815950)
Workaround: Contact Support for assistance.
Organization
74853 / SCCORE-1547
Summary: The Organization drop-down in the banner does not revert to the default Organization for a user that is in two Child Organizations if one of those Child Organizations, where the user is the last user, is deleted. The remaining Child Organization should become the default, but it does not. (Case # 69779, 01729899, 01771521, 01786593)
Workaround: None.
65988 / SCCORE-1536
Summary: Exporting Subscription information for Child Organizations to CSV after sorting in the TIBCO Scribe® Online User Interface causes the counts and Child Organizations not to match between the spreadsheet and the User Interface. (Case # 65227, 01725375)
Workaround: Sort the data in the spreadsheet after export instead of in the TIBCO Scribe® Online User Interface.
Solutions
SCCORE-7466
Summary: Cloud Services are sometimes moved to a new server for load balancing purposes. When an agent is moved it could cause a fatal error with a running Solution and fail to process data. The error message is similar to the following: (Case # 02062946, 02063491)
Could not find the AdapterType Id '00000000-0000-0000-0000-000000000000'
Workaround: These errors typically correct themselves. If the error does not correct itself, you can temporarily assign the Solution to an On-Premise Agent, then assign it back to a Cloud Service.
SCCORE-6956
Summary: Solutions containing Maps using the REST Connector that are edited frequently, may generate errors similar to the following: (Case # 01952130, 02061798)
Message: Unexpected error during execute query for processDefinition 0a76e0ef-4c03-4611-ae1e-2b832dbcaeed
Workaround: Export the Maps and reimport them into a new Solution.
SCCORE-6203
Summary: The Solution status "Waiting to restart, memory limit reached" is displayed but the Agent fails to restart. (Case # 01924661, 01930791, 01763160, 01859499)
Workaround: Restart the Agent manually.
SCCORE-6193
Summary: A Scheduled or On Demand Solutioin remains in a running status indefinitely. Attempting to stop the Solution causes the state to stay in an In Progress or Stopping status. (Case # 01924753, 01925865, 01926089)
Workaround: Stop and restart the On-Premise Agent or provision a new Cloud Service.
SCCORE-5030
Summary: The Agent assigned to a Solution scheduled to run at frequent intervals is changed to a new Agent. The schedule for the Solution is not deleted from the first Agent causing both Agents to attempt to run the Solution. The Solution fails with timeout errors. (Case # 01898489)
Workaround: Completely remove the first Agent by deleting it from the User Interface and also using the Windows Remove Programs option to remove the associated Agent service.
SCCORE-1754 / SCCORE-2848
Summary: If an API server does not remain on the service bus and switches to polling, there is a noticeable performance degradation when running Solutions. (Case # 01821718, 01881448, 01827974)
Workaround: None. The issue will resolve itself over time.
SCCORE-532
Summary: Solutions containing Message Maps that are disabled validate the Connections configured in those Maps. If the credentials in the Connection are no longer valid TIBCO Scribe® Online attempts to validate the Connection continuously. This can cause login rate limits to be exceeded and prevent valid Connections from connecting successfully. (Case # 01782007)
Workaround: Delete the disabled Maps, correct the credentials for the Connections in the Maps, or export the Maps and import them into a disabled Solution to archive them.
75416 / SCCORE-142
Summary: In some cases where a single Agent is used to run high volume Message Maps, Replication Solutions, and Integration Solutions, the volume causes Connections to fail and the Agent to stop processing inbound messages. If a message has already been deleted from the queue but has not been processed by the Map, the message may be lost. Errors similar to the following are generated: (Case # 70022, 01730141)
MessageProcessExecutor
Message : Count must be positive and count must refer to a location within the string/array/collection.
Parameter name: count
CacheConnectManager
Exception Type : IndexOutOfRangeException
Message : Index was outside the bounds of the array.
Workaround: Restart the Agent to revive the Connections. Consider using more than one Agent.
67116 / SCCORE-147
Summary: When a fatal error is generated for an Event Solution with multiple Maps, there is no indication of which Map caused the error. (Case # 66033, 01726167)
Workaround: None.
63600
Summary: Running a Replication Solution that updates existing records generates duplicate key warning errors because the records already exist in the target database. During replication when a record is sent to the target database, if it does not exist the record is added, if it already exists the existing record is deleted and the new record is added. (Case # 64580)
Workaround: These errors can be ignored for Replication Solutions, but should be researched and resolved for Integration Solutions.
38935
Summary: In an Organization that only has a Subscription for Replication Solutions, delete is disabled for Solutions.
Workaround: Contact Support to add an Integration Subscription. This enables the delete option for Solutions.
36258
Summary: Changing the order of Maps in a Solution while the Solution status is changing from “Preparing” to “On Demand” may cause the user interface for the Maps to display incorrectly with overlapping text. (Case # 55748)
Workaround: Return to the Dashboard, then open the Solution again.
Subscriptions
-
User Interface
63399
Summary: When running TIBCO Scribe® Online in some versions of Chrome, such as v65, columns are not resizeable.
Workaround: This has been resolved in version 73 of Chrome. Upgrade to the latest version of Chrome or open TIBCO Scribe® Online in another supported browser.
