Known issues

The following known issues exist:

 

[HULFT Square site]

  • Common

    • If you change contractors, contact support.

    • As a guideline, if you have 5,000 or more files and directories placed directly under a single directory, a timeout error may occur.

      Use a hierarchical directory or other such means to avoid increasing the number of files and directories in a single directory by too much.

      The following are affected.

      • Designer > Get List of File Names operation

      • Designer > Storage file chooser

      Scripts may be executed successfully.

    • Quick filter

      If you move from a page or directory while the quick filter is being used, although it appears that the filter has been cleared, it may still be applied.

      Workarounds

      Enter characters into the quick filter again, and then clear them.

  • HULFT Application Migration

    HULFT Transfer Migration

    When you import settings with a migration tool, some fields may be blank. The import itself succeeds.

    Workarounds

    Open settings and set the appropriate values using the UI.

  • > All

    In the message widget, the messages are displayed in Japanese even in an environment where the language is set to English.

  • > APPLICATIONS

    • If an application that has been updated with 2024.2.2 or later and includes calling a script is created, and then edited or cloned using the application menu, an error will occur when you press Test after pressing Configure.

    • When you undeploy an application and select Reconfigure in order to change the API path when the trigger condition for the application is REST API, the changed path isn't reflected.

      Workarounds

      • If Redistribution policy is redistributable
        Use Clone & Edit on the details screen of the application to clone the application and change the API path.

      • If Redistribution policy is non redistributable
        Create a new application.

      (September 13, 2026)

    • If you edit an application when the trigger condition for the application is REST API, the behavior may become unstable.

      (September 13, 2026)

  • > APPLICATIONS > HULFT Transfer App

    If you insert a space into the file path that includes the file name in the Send configuration or Receive configuration, transfer will fail.

  • > SERVICES

    • To use native applications, the Application admin permission is required in addition to the permission for each native application.

    • Even if a user has the FullAccess permission for each application under SERVICES (SFTP, HULFT App, or HULFT Transfer App), the service list screen isn't displayed.

      Workarounds

      Assign the ApplicationFullAccess permission to the user.

      When using a predefined group, assign Developer, TechnicalSupport, SystemOperator, or Admin to the user.

      (September 13, 2026)

  • > SERVICES > HULFT Integrate

    • The region for a HULFT Integrate service can't be specified.

    • When you add a new HULFT Integrate service, the service takes approximately 5 minutes to start. Scripts and jobs can be executed with the service after the service starts.

    • If some kind of error occurs during Designer execution or other such cases and the HULFT Integrate service stops unexpectedly, contact support.

    • When you attempt to view the list, a 500 error may occur.

    • If you create a service with a name that is identical to that of an existing service, creation is completed successfully, but creating it with a different service name is recommended.

    • JVM Non-Heap Memory and CPU for a HULFT Integrate service may show 0% even if you have not stopped or restarted the service.

  • > SERVICES > HULFT Transfer

    • Even users who are granted the ListTransferService permission can't view the list of services.

      Workarounds

      Grant the user the ViewTransferService permission.

    • The status may be blank.

    • If you create a service with a name that is identical to that of an existing service, creation is completed successfully, but creating it with a different service name is recommended.

    • If you attempt to delete a HULFT Transfer service that is linked to VPCEndPoint, an error may be displayed.

  • > SERVICES > SFTP

    • If you rename a file from an SFTP client, the file isn't renamed, but is instead deleted.

      Workarounds

      Rename files from > SERVICES > Storage in HULFT Square.

    • An SFTP service with a memory leak may restart after a certain amount of time.

      (September 13, 2026)

    • When you attempt to register a large number of users in SFTP, an error may occur, leading to a failure to start.

      (September 13, 2026)

  • > SERVICES > HULFT Transfer App

    If a HULFT Transfer App service is restarted as a result of maintenance or such on AWS, file transfer may fail.

    Workarounds

    From > APPLICATIONS > HULFT Transfer App, undeploy HULFT Transfer App that is currently deployed, and then deploy it again.

  • > SERVICES > HULFT Transfer App

    > SERVICES > HULFT App

    • If the PrivateLink outbound settings that were specified for the service when the application was deployed are deleted, undeploying the application fails.

      Contact support if this this situation occurs.

      (September 13, 2026)

    • If you change a setting value such as the port number and then change the settings again before the service becomes available, it may result in unintended settings being applied.

      This situation is more likely to occur if multiple users configure the setting values for a service simultaneously. You may encounter other issues with a service in this state, such as being unable to delete the service. Contact support if this this situation occurs.

      (September 13, 2026)

  • > HULFT INTEGRATE > Projects

    When you create multiple levels of folders under a project in Designer, if you place a script in the second level or after, an error occurs when you try to change the name of a project from the detailed information screen for the project.

  • > HULFT INTEGRATE > Connections

    • When you create a connection resource for a project used in a shared workspace, create the connection resource in the corresponding workspace.

      If you specify a connection resource in the Personal workspace or a workspace to which the user doesn't have access rights, unexpected operations may occur.

    • When creating the following connections, selecting or clearing the checkbox for SSL connection doesn’t change the URL field on the screen:

      • Amazon RDS for PostgreSQL 12 connection

      • Amazon RDS for PostgreSQL 15 connection

      • Amazon RDS for PostgreSQL 16 connection

      • Amazon Aurora for PostgreSQL 16 connection

      • Amazon Aurora for PostgreSQL 17 connection

      Selecting the checkbox for SSL connection enables SSL for the actual connection.

      (September 13, 2026)

  • > HULFT INTEGRATE > Connections> Amazon RDS for SQL Server 2017 connector

    If you select the checkbox for Enter URL directly for Amazon RDS for SQL Server 2017 connection, the connection test may fail.

    Workarounds

    Clear the checkbox for Enter URL directly.

  • > HULFT APP > Receive Configs

    > HULFT TRANSFER APP > Receive Configs

    If Restore is set for Error handling in the Receive configuration, receive files may be deleted.

  • > API MANAGEMENT > API Projects

    • Use only alphanumeric characters for API project names.

    • When you select OPTIONS method, you can edit the request body, but when you enter a value, an error occurs.

    • When basic paths and resource strings are combined, it may result in creation of multiple jobs with the same URL when string concatenation is performed. If this occurs, a job that you did not intend may be executed.

      Workarounds

      Configure settings so that multiple combinations of base paths and resource strings will not result in the same URL.

  • > JOBS

    • If a large number of versions of a script are used, loading may slow down.

    • During creation or editing of a job, when you select the Finish or Apply button, a timeout error (Unexpected error Endpoint request timed out) may occur.

      Communication may time out because the processing is taking a long time due to a large number of versions or other reasons. The processing continues in the background and may be completed even if this error occurs.

  • > JOBS > Applications

    • If a scheduled job was made into an application at 2023.4 release, it's displayed in the list after the 2024.1 release is applied. However, , which indicates an application is stopped, may appear for an application that is running.

      Workarounds

      On the application settings screen, selecting Deploy in Profile changes the icon to the one that indicates that an application is running.

  • > JOBS > REST API Jobs

    • If you turn off or turn on a job with Turn off job or Turn on job, the user listed for Last modifier is set as (N/A).

      This doesn't cause any problems for execution of the job, but it prevents you from identifying the job by filtering or searching by last modifier.

      Workarounds

      When you turn off a job, if you edit the comment in Description, the name of the last modifier is recorded.

      There are no workarounds for when you turn on a job.

    • If the number of jobs displayed at a time exceeds 50, an "Internal Server Error" occurs.

      Workarounds

      Ensure the number of REST API jobs that belong to one workspace remains at 50 or fewer. Set which workspace displays the jobs if it hasn't been set.

    • If the <xml> tag exists in the body, a 403 error occurs.

      Workarounds

      Don't include the <xml> tag.

    • When you create an application from a REST API job, if multiple scripts of the same version are included in a single project and used by a single API project, an error occurs.

    • When REST API jobs are disabled, if you call such a REST API, instead of a 503 Service Unavailable error, a 403 Forbidden error is returned.

    • If the following conditions are fulfilled when you execute a REST API job, the API response body will be blank.

      • The exit status (return value) of the script is 1 or higher

      • The response body is set in the API project response settings

      • Asynchornous execution is not specified

  • > JOBS > Schedule Jobs

    • For a script that uses Call Script, if you create a scheduled job with Always apply the latest set for the dependency relationship, update a calendar, and then turn off or turn on the job, the latest script is not applied.

      Workarounds

      Update the scheduled job itself and then turn off or turn on the job to apply the latest script.

    • On the dialog where you can enable or disable scheduled jobs, depending on when you press OK, in rare cases, multiple scheduled jobs may be enabled.

  • > Detailed logs

    If the size of the detailed script log exceeds 10 MB due to thrown exceptions or other reasons, the log may not be exported successfully.

  • > Application > All

    Even if you select REST API from Trigger in the filter, the results aren't displayed correctly.

    (September 13, 2026)

  • > SERVICE EVENTS > HULFT Integrate

    For certain connectors, when multiple threads are executed simultaneously, such as with Parallel Stream Processing (PSP), the language setting of some threads may change. As a result, some log records may be output with the changed language setting.

  • > SERVICE EVENTS > HULFT Transfer

    • The status on the list screen and the status on the details screen may be different. In such cases, confirm the status on the details screen.

    • When a V7 compatible transfer is performed, the following log records might not be displayed:

      • Log records with a status of transferring in the list view

      • Log records of the transfer start result in the detailed view

      Note that log records of completed transfers are displayed.

  • > SERVICE EVENTS > HULFT Transfer App

    The profile name displayed on logs is fixed to the first profile deployed for each service.

    Workarounds

    When you switch the HULFT Transfer App profile to deploy, undeploy and then restart the HULFT Transfer App service to update the profile information displayed on logs.

  • > SERVICE EVENTS > SFTP

    If you change the name of the SFTP service, logs cease to be displayed.

    Workarounds

    Change the name back and they will be displayed.

  • > USER MANAGEMENT > Users

    • Even if you enter the Middle Name, Profile, and Department fields as blank and update, the values set previously may still be displayed.

    • If the group linked with an invited user is deleted before the user completes registration, the following error will appear on the screen during the registration process, causing the user registration to fail:

      Groups cannot be null or empty

      Workarounds

      Don't delete a group linked with invited users.

      (September 13, 2026)

  • > USER MANAGEMENT > Groups

    Group names can't be changed.

  • > ACCESS MANAGEMENT > Policies

    • The permission InviteUser is not included in UserGroupFullAccess.

    • Even if the PrivateLinkAdminAccess permission is set, if you specify Privatelink for Secure connection type when creating an SFTP service, the connections are not displayed on the list for Secure connection.

      Workarounds

      For those who intend to create an SFTP service, add one of the following permissions:

      • ListPrivateLink

      • PrivateLinkFullAccess

  • > NETWORK > PrivateLink

    • Even if the status is updated in Approval Requests that is displayed from Allowed Accounts in Inbound in PrivateLink, the date and time displayed in Updated are not updated.

    • If a job consists of a connection that is configured to use an alias and a script, the information of the job is not displayed as outbound traffic on PrivateLink.

  • > Notifications > General

    > Notifications > Email

    After you modify the settings of Notifications or Email Notifications, it may take up to 10 minutes for the modifications to be reflected in the actual operation.

  • Personal Settings > Change Password

    When you reset the password, you can enter multibyte characters, but you can't use a multibyte password. Be sure to use single-byte characters on password.

  • The check function for restricted characters isn't implemented yet.

    If you use restricted characters, errors or unexpected operations may occur.

  • The check function for input characters may be insufficient.

    If you enter invalid characters, errors or unexpected operations may occur.

  • Error messages may not come up, or even if they do come up they may be unclear.

 

[Designer]

  • During processing for which PSP processing is enabled, even if you use Get Value by XPath, no exception occurs.

  • If a user who doesn't belong to a predefined group such as Admin or Developer opens Designer, a dialog may appear indicating that functions are limited due to lack of permissions. If the permissions displayed are not those described in the manual, operations are not affected.

  • If a script name contains an underscore, the underscore may not be displayed correctly in the tab in Designer.

  • When you display the online document in Designer with the F1 key:

    If you press the F1 key in the Mapper editor, the relevant page is shown, but other than that, only the portal page of the online document is shown.

  • Handling of file names that include certain characters such as + may fail.

  • With debugging, even if the debugging is completed, when certain conditions are met, it may be treated as still executing on Designer.

    In that case, if you click the Stop button, an error occurs because the script has already completed.

    For the completion of execution of the script, check the application log.

  • In Designer, when you connect Mappers, even if Load schema from components/files is specified for the input data for the second Mapper, indexes aren't added automatically. All of the data is treated as the first field of the output schema.

    This phenomenon also occurs when you set the output schema for the first Mapper and then draw the data flow to the second Mapper.

    Workarounds

    Set the input schema manually for the second Mapper and after.

  • If you create a project in one workspace with the same name as a project in another workspace and then call a script, an error may occur.

  • The null value is replaced with the characters "null" when the following conditions are satisfied:

    • The output variable of Call Script is set for the input variable of another Call Script.

    • The value of the output variable is null.

    Workarounds

    Instead of setting the output variable of the first Call Script for the input variable of the second Call Script, pass the value of the output variable to the script variable and then set the input variable of the second Call Script via the script variable.

  • If you change the values of the following properties in "Loop" and "Loop by Number of Data", the change might not be detected or saved.

    • Loop

      • Property items in the Log settings tab

    • Loop by Number of Data

      • Number of data in one loop in the Required settings tab

      • Separation path in the XML data processing tab

      • Property items in the Log settings tab 

    Workarounds

    Changes are detected when a comment in the Comment tab is edited. An update mark will be displayed on the operation icon to identify the changes.

  • If you try to perform an upsert operation to double type fields in the Upsert Records operation for the Salesforce (deprecated) connector, it fails and displays an error.

    Updates and inserts behave correctly.

    This phenomenon does not occur on the Salesforce connector. The Salesforce (deprecated) connector is not recommended. Use the Salesforce connector.

  • Snowflake connector

    When the Snowflake connector and JDBC connector are used for the Snowflake connection, an error occurs if you read the TIMESTAMP_TZ or TIMESTAMP_LTZ type data and draw a data flow directly from the data to the join operation.

    Workarounds

    Try the following:

    • Convert the data from date and time type to string type in the Execute Select SQL operation before the data is read.

    • Convert the data to string type, either by using the date/time formatting logic in Mapper or by other methods.

    (September 13, 2026)

  • Excel connector

    • If the extension of the Excel file is uppercase, an error may occur.

      Workarounds

      Make sure that the extension of the file name is lowercase.

    • An error occurs if you attempt to use a non-existent path or variable for the workspace name in the file path for the following operations of the Excel connector:

      • Read from Named Range

      • Rename Sheet

      • Delete Sheet

      • Copy Sheet

      When this error occurs, you can't open the relevant operation. Saving it in this state will prevent you from opening the script.

      Workarounds

      If you can no longer open the script, specify a version prior to making the above edit and open the script.

      (September 13, 2026)

  • SAP S/4HANA OData connector

    Even if you select Add or Edit list for connection resources in the Required settings tab for each operation, the appropriate screen isn't displayed. Instead, the following screens are displayed for each option:

    • Add

      > HULFT INTEGRATE > Connections > Add

    • Edit list

      > HULFT INTEGRATE > Connections

    Workarounds

    Open the settings screen from > SAP S/4HANA ODATA > OData Connection and then configure the settings.

    From the tool palette in Designer, drag an operation onto the script canvas and select a connection resource from the list of connection resources.

    If you add the setting after placing a component icon, the setting may not be displayed in the list.

  • Amazon RDS for MySQL 8.4 connector

    When an item name includes the string "into", an AMAZONRDS001E error occurs if the SELECT statement is executed.

    Workarounds

    To avoid this issue, use single quotation marks to escape it, like this: ‘ainto’.

    (September 13, 2026)

  • Amazon S3 connector

    When using access key authentication

    If your IAM user is granted read and write permissions to an S3 bucket on an account that isn't your IAM user's account, files in this bucket on S3 can be read and written, but operations will fail on the S3 connector, so data can't be read or written.

    When using IAM role authentication

    When IAM role ARN is specified for a connection resource, even if the access key has not been shared, the bucket can be accessed by other accounts.

  • Kintone connector

    Some API call functions can't be used with the Kintone connector.

    bulkRequest/post 
preview/app/reports/put 
app/settings/get 
preview/app/settings/get 
preview/app/settings/put

  • HULFT connector

    The component variable exit_status in the Send File operation of the HULFT connector stores the HTTP status code rather than the exit status of the Send File command (utlsend).

  • Database category connectors

    If 253 characters are set for Host name, connection may fail.

 

[Online document]

  • Some of the screen images used in this document may differ slightly from the actual screens.

  • Differences may exist between the contents of the Japanese and English versions depending on the translation schedule for updated content in the online document.

Policies     (c) Saison Technology Co.,Ltd. 2021

TOP