menu

Feed available - Subscribe to our feed to stay up to date on upcoming maintenance and incidents.

Kony Cloud status
Current status and incident report

V9 Foundation Release

Maintenance window: January 13, 2020 00:01 to 04:00
The maintenance window start and end times are local to the region in which your Clouds are hosted. If you are unsure where your Clouds are hosted, you can hover over a Cloud Name in the Manage Clouds page of the Cloud Management Console and the region will be displayed.

This release includes updates to the backend components of Fabric on the Cloud (Identity, Workspace, Console, Engagement) only and lays the foundation for the full V9 release of Quantum (Visualizer + Fabric) that will be available in the first half of 2020. Upgrading the core Fabric Runtime server environments on the cloud to V9 will not be available to customers until the full release of Quantum V9.

With this release, Identity, Workspace, Console, and Engagement are being updated with a set of incremental features described below that can be used immediately and will work with the current V8 version of Visualizer. Since this update provides the foundation for the full V9 release, you can get additional details on what is coming in the full Quantum V9 release by viewing our V9 Roadmap webinar on Base Camp.

The Certificate Authority (CA) for SSL/TLS certificates for all database instances in our Cloud PaaS expires in March. During this maintenance window, we plan to update the certificates to reference the new CA. We anticipate that the database instances will be unavailable for a few minutes at most as we update the certificates.
Impacted Cloud services:
  • Cloud Management Console

    • Feature level access

      Admins can restrict access to specific features of the Fabric environment, such as the App Services, Engagement services, Logging Console, etc.

      • Added support for a Build Client App only feature
      • The Build Client app role allows developers to be able to build apps by pointing to a production environment from Kony Visualizer, without the ability to publish any services or access to the Fabric admin console. This effectively works like a read-only role for app developers.
    • Enhanced the security in the Quantum app by adding support for primary and secondary appkey and appsecret.

      The primary and secondary keys are packaged with the web and native channels respectively when their apps are built in Kony Visualizer.

      • Added ability to rotate appkeys
      • Different appkeys for web and native with ability to rotate keys.
    • Added support for the parameter prompt

      As part of OIDC authorization to improve the logout flow while using the OAuth Provider.

    • Added support for sending push notification to EAS

    • Added support to create the app service document based on the alias hostname.

    • Added support to access custom features of Kony Fabric environments.

    • Simplified the object model definition - field names and types.

    • Support to generate Object model by importing an MS Excel file, for Storage.

      Developers can create data model for objects in an Object Service by using the column data in MS Excel.

    • Added support to download the reconfigurations made to an app before publishing.

      When an app has been reconfigured before publish the reconfiguration information is available for viewing from App publish snapshots.

    • Added support for import and export of configurable server/client parameters (App Services) through MFCLI.

  • Identity

    • Restrict Identity services for server-to-server access

      To differentiate the security mechanisms between client-to-server and server-to-server communication, the ability to restrict Identity services for the server-to-server communication has been provided.

    • Enhanced the custom identity adapter

      For supporting additional pass-through endpoints like user attributes, security attributes, and Multi Factor Authentication (MFA).

    • Added support for Sign-Up in Kony User Repository

      The Sign-up option allows the user to sign-up or register to the application by using their e-mail ID.

    • Added concurrency options for Identity services

      Options have been added to the Identity services to allow users to control the desired behavior for concurrent logins.

    • The Single Sign-On option is available in Kony Visualizer

  • Offline Objects

    • Added support for Hierarchical Uploads for the Web platform

    • The Offline Objects and Generating Models’ features are available in Kony Visualizer

    • Added object-level support for clearing the offline data.

  • Analytics

    • Export Standard Reports in Excel format

      Added support to export standard chart-based reports in Excel format.

    • Added support to install a new version app link while launching the Kony Fabric Mobile App. Deprecating support to the older version of Kony Fabric Mobile App.

  • App Factory

    • Build and publish Apps across clouds and cloud accounts using AppFactory.

      Allow users to build and publish apps to Docker images and Azure cloud from the AppFactory console.

    • Run your Jasmine test scripts on AppFactory for Native apps, Responsive web apps, and Progressive web apps as part of your build process on devices or on the latest Google Chrome browser.

      • Receive comprehensive results from each Jasmine Test run via email or review your test in AppFactory’s testing console.
      • The Jasmine testing framework is incompatible with the Cordova and web browser widgets with this release.
      • The Jasmine testing framework cannot test OAuth based logins with this release.
  • Engagement

    • Added support  for Application API key to enhance security

      Added new APIs for the creation, modification and deletion of the App API key.

      Enhanced the console to support the management of the newly added App API key feature.

    • Enhancement of the Email API

      Enhanced the email API to use templates to send emails.

    • Enhancement of the Push API

      Enhanced the Push API to return user defined key value pairs in the payload.

    • Added Support for Salesforce SMS Aggregator

      Added support for the new Salesforce SMS aggregator to send SMS messages in the Console.

      Enhanced existing APIs to support the creation and the management of the Salesforce SMS aggregator.

    • Added custom parameters to the Fetch Push API

  • IQ

    • Utterance fulfillment suggestions

    • Searching hikes catalog is now available, along with Base Camp forum, docs, and videos

    • Improved search results for documentation

    • Context and user intent based auto updation of the placeholder text in chat window panel

    • Intelligent re-connection attempts through web sockets during intermittent network issues

    • JWT claims token based socket request authentication mechanism

    • Bug fixes

  • Workspace

    • Support for Cloud Management Console changes

  • Developer Portal

    • Support for Cloud Management Console changes


Impact Level : minor

No significant downtime is expected for the impacted Cloud services while this maintenance is being performed. We expect at most a few minutes of downtime as we update SSL/TLS certificates for each database instance. The scheduled maintenance is designed to mitigate disruptions to service availability and performance for the impacted Cloud services. However, it is possible for the impacted Cloud services to be unavailable and/or performance degraded for a short period of time during the maintenance window. Note that no changes are being applied for other Cloud services outside of the list of impacted services above and no service availability or performance disruption is expected for other Cloud services.

Release summary details (including any impacts) may be updated as we near the release date.

[2020-01-09 20:32 UTC]

  • Add IQ, Workspace, and Developer Portal release summaries.
  • Add note that a very small window of downtime will be expected as we update SSL/TLS certificates for each database instance in our Cloud PaaS.

[2020-01-13 07:00 UTC] All Asia and European regions are completed without incident, along with Sao Paulo. We are expecting impacts to Identity as the in-place migration for the Virginia region cannot be completed as planned.

[2020-01-13 08:00 UTC] We have reverted the deployment for one of the Identity clusters in Virginia, and have involved development. The number of extended and abandoned sessions has crossed a threshold and can’t be completed as planned.

[2020-01-13 09:15 UTC] We have developed a workflow that will involve truncating certain data tables in order to complete the v9 upgrade. The impact will be that users with a longer than recommended session duration set, one that would last overnight or longer, will have to re-login to applications (equivalent to any normal session expiration).

[2020-01-13 10:20 UTC] Deployment issues caused by the timing of an update has caused an unplanned outage for some customers in Virginia. One of the three Identity clusters was impacted. We are working to get that cluster back in service.

[2020-01-13 11:30 UTC] Resolved. Identity services are restored. Some Kony customers in the Virginia region may have to logout and log back into manage.kony.com. Some Application users will need to log back into their apps if they were being hosted on the single Identity cluster in Virginia that was affected.

Tokyo performance degradation

Incident window: December 17, 2019 10:15 to 11:30
November 21, 2019 00:01 to 04:00
Impacted Cloud services:
  • Cloud services in Tokyo

    • Issue affects all customers using multi-tenant Identity services in Tokyo


Impact Level : high

The performance and availability of Cloud services in other regions are not impacted.

[2019-12-17 09:50 UTC] Excessive activity on Identity in the Tokyo region.

[2019-12-17 10:20 UTC] Database capacity exceeded and we are working to determine the cause and restore services.

[2019-12-17 11:28 UTC] Resolved. Space issues resolved and Identity services in the Tokyo region are responding normally.

Cloud Management Console and Workspace Services Hotfixes

Maintenance window: December 9, 2019 00:01 to 04:00
The maintenance window start and end times are local to the region in which your Clouds are hosted. If you are unsure where your Clouds are hosted, you can hover over a Cloud Name in the Manage Clouds page of the Cloud Management Console and the region will be displayed.
Impacted Cloud services:
  • Cloud Management Console

    • Fix RDBMS services not loading issue occurring after Fabric upgrade

  • Workspace

    • Fix RDBMS services not loading issue occurring after Fabric upgrade


Impact Level : minor

No downtime is expected for the impacted Cloud services while this maintenance is being performed. The scheduled maintenance is designed to mitigate disruptions to service availability and performance for the impacted Cloud services. However, it is possible for the impacted Cloud services to be unavailable and/or performance degraded for a short period of time during the maintenance window. Note that no changes are being applied for other Cloud services outside of the list of impacted services above and no service availability or performance disruption is expected for other Cloud services.

Workspace Services Hotfix

Maintenance window: November 21, 2019 00:01 to 04:00
The maintenance window start and end times are local to the region in which your Clouds are hosted. If you are unsure where your Clouds are hosted, you can hover over a Cloud Name in the Manage Clouds page of the Cloud Management Console and the region will be displayed.
Impacted Cloud services:
  • Workspace

    • Display custom error page and handle 404 not found error


Impact Level : minor

No downtime is expected for the impacted Cloud services while this maintenance is being performed. The scheduled maintenance is designed to mitigate disruptions to service availability and performance for the impacted Cloud services. However, it is possible for the impacted Cloud services to be unavailable and/or performance degraded for a short period of time during the maintenance window. Note that no changes are being applied for other Cloud services outside of the list of impacted services above and no service availability or performance disruption is expected for other Cloud services.

Cloud Management Console Release

Maintenance window: November 18, 2019 05:00 to 09:00 UTC
Impacted Cloud services:
  • Cloud Management Console

    • Add Excel as available export option for chart-based standard reports


Impact Level : minor

No downtime is expected for the impacted Cloud services while this maintenance is being performed. The scheduled maintenance is designed to mitigate disruptions to service availability and performance for the impacted Cloud services. However, it is possible for the impacted Cloud services to be unavailable and/or performance degraded for a short period of time during the maintenance window. Note that no changes are being applied for other Cloud services outside of the list of impacted services above and no service availability or performance disruption is expected for other Cloud services.

Cloud SSL Certificate Updates

Maintenance window: November 16, 2019 00:01 UTC to November 17, 2019 00:01 UTC
Impacted Cloud services:
  • Cloud SSL certificates for Identity services (.auth.konycloud.com), Engagement services (.messaging.konycloud.com), App services (.konycloud.com), and Sync services (.sync.konycloud.com)

    • ⚠️ Note: If you have not pinned Kony certificates in your application, no application updates will be necessary. Customers that have pinned SSL certificates will need to download the new certificates, rebuild the applications, including both the old and new certificates, and publish the updated binaries to the various app stores. Your applications should be published before Kony updates the certificates on the cloud servers or customers will no longer be able to connect. New certificates can be found on the Kony Cloud Certificate Preview page. The new certificates can also be downloaded by executing the following commands:

      • Identity: openssl s_client -showcerts -connect konycertificatepreview.auth.konycloud.com:443

      • Engagement: openssl s_client -showcerts -connect konycertificatepreview.messaging.konycloud.com:7443

      • App: openssl s_client -showcerts -connect konycertificatepreview.konycloud.com:8443

      • Sync: openssl s_client -showcerts -connect konycertificatepreview.sync.konycloud.com:9443

    • Customers who have pinned the public key instead of the full certificate (which we strongly recommend and was made available in V8 SP4) may not be required to update their applications. The updated certificates will have the same public keys as the existing certificates.

      • If necessary, you can submit your applications for expedited approval (e.g., Apple has an expedited approval process for critical bugs, or in this case, pinned certificates).


        Impact Level : high

        Customer applications that have pinned SSL certificates will need to be updated as described above prior to this maintenance window. Customer applications that have not pinned SSL certificates will not be affected and will experience no service disruptions during this maintenance window.

        Please refer to our documentation for how to pin the public key of a certificate (which we strongly recommend and was made available in V8 SP4) or how to pin an SSL certificate in your apps (deprecated).

        Integration Server V8 SP4 FP3 HF8 Release

        Maintenance window: November 11, 2019 00:01 to 04:00
        The maintenance window start and end times are local to the region in which your Clouds are hosted. If you are unsure where your Clouds are hosted, you can hover over a Cloud Name in the Manage Clouds page of the Cloud Management Console and the region will be displayed.
        Impacted Cloud services:
        • Integration Server

          • Fix inconsistent formatting of x-kony-reportingparams in request headers when application invokes integration service. In this case, it is url encoded, which is not correct. Instead, it should be returned as a json string, similar to how it is returned via Object service.

          • ⚠️ Any existing Clouds containing dedicated (i.e., single-tenant) Kony Integration Server runtime environments will NOT be affected during the maintenance window (i.e., will NOT be automatically upgraded). If you wish to upgrade, please open a support case, specifying your Cloud(s), desired version (V8 SP4 FP3 HF8), and desired maintenance window (day, time, and timezone) when we can apply the upgrade. Existing Clouds containing shared (i.e., multi-tenant) Kony Integration Server runtime environments (e.g., AppPlatform Gold & Platinum tiers (excluding Platinum Plus), free Fabric services) WILL be automatically upgraded during the maintenance window. For additional details regarding this hotfix, please refer to our release notes page, which will be updated in the next few days with notes for this latest release.


        Impact Level : minor

        No downtime is expected for the impacted Cloud services while this maintenance is being performed. The scheduled maintenance is designed to mitigate disruptions to service availability and performance for the impacted Cloud services. However, it is possible for the impacted Cloud services to be unavailable and/or performance degraded for a short period of time during the maintenance window. Note that no changes are being applied for other Cloud services outside of the list of impacted services above and no service availability or performance disruption is expected for other Cloud services.

        Workspace services - Oregon is unavailable

        Incident window: November 8, 2019 22:16 UTC to 22:48 UTC
        Impacted Cloud services:
        • Workspace (Oregon region only)

          • Other regions are not affected


        Impact Level : high

        Workspace services in Oregon have become unavailable starting at 22:16 UTC. The availability and performance of Workspace services in other regions is not affected. We are investigating.

        [2019-11-08 22:48 UTC] Resolved. The underlying Oregon Workspace database master node had failed and automatically failed over to the replica node, which had been promoted as the new master (and a new replica created after). However, while the database was able to recover with our automation, the Oregon Workspace application did not automatically recover as would be expected and was still yielding errors until we intervened by restarting. Once restarted at 22:48 UTC, the Oregon Workspace services have been available and performing within expected levels. We will be continuing to monitor. We will also be continuing to coordinate with our development team to identify why the Workspace application was unable to automatically recover and to work toward a solution to mitigate these types of incidents requiring our attention beyond our automated incident response controls in the future.

        Workspace services - Oregon is unavailable

        Incident window: November 7, 2019 16:30 UTC to 16:45 UTC
        Impacted Cloud services:
        • Workspace (Oregon region only)

          • Other regions are not affected


        Impact Level : high

        Workspace services in Oregon have become unavailable starting at 16:30 UTC. The availability and performance of Workspace services in other regions is not affected. We are investigating.

        [2019-11-07 16:59 UTC] Resolved. The underlying Oregon Workspace database master node had failed and automatically failed over to the replica node, which had been promoted as the new master (and a new replica created after). However, while the database was able to recover with our automation, the Oregon Workspace application did not automatically recover as would be expected and was still yielding errors until we intervened by restarting. Once restarted at 16:45 UTC, the Oregon Workspace services have been available and performing within expected levels. We will be continuing to monitor. We will also be continuing to coordinate with our development team to identify why the Workspace application was unable to automatically recover and to work toward a solution to mitigate these types of incidents requiring our attention beyond our automated incident response controls in the future.