We experienced an issue affecting customizations for which “Register to kintone App” was executed between approximately 5:40 p.m. and 6:15 p.m. on May 28, 2026, whereby execution of the customization was not permitted.
The issue has now been resolved.
We sincerely apologize for any inconvenience caused to our users.
■ Date and Time of Occurrence
From approximately 5:40 p.m. to 6:15 p.m. on May 28, 2026
■ Recovery Procedure
Customers who executed “Register to kintone App” during the above time period should open the customization settings and press the “Register to kintone App” button again to re-register the customization.
■ Details of the Issue
When “Register to kintone App” was executed while the issue was occurring, a customization file was created in a state where the correct license check could not be performed.
次の場所のその他のトピック:
Maintenance and incident announcement / 障害・メンテナンス情報
[R3] Support
平素はgusuku Customineをご利用いただき、誠にありがとうございます。
2026年5月28日 午後5時40分頃から午後6時15分頃の間に「kintoneアプリへ登録」を実行したカスタマイズについて、カスタマイズの実行が許可されないという問題が発生しておりました。
現在は復旧しております。
ご利用中のユーザー様には、ご不便をお掛けしましたことをお詫び申し上げます。
■ 発生日時
2026年5月28日 午後5時40分頃から午後6時15分頃まで
■ 復旧手順
上記時間帯に「kintoneアプリへ登録」を実行されたお客様に関しましては、
カスタマイズの設定を開いて、そのまま再度「kintoneアプリへ登録」ボタンを押して登録し直してください。
■ 障害の内容
障害発生中に「kintoneアプリへ登録」を実行した際、正しいライセンスチェックが実行できない状態のカスタマイズファイルが作成されていました。
Thank you very much for using gusuku Customine.
We experienced an issue affecting customizations for which “Register to kintone App” was executed between approximately 5:40 p.m. and 6:15 p.m. on May 28, 2026, whereby execution of the customization was not permitted.
The issue has now been resolved.
We sincerely apologize for any inconvenience caused to our users.
■ Date and Time of Occurrence
From approximately 5:40 p.m. to 6:15 p.m. on May 28, 2026
■ Recovery Procedure
Customers who executed “Register to kintone App” during the above time period should open the customization settings and press the “Register to kintone App” button again to re-register the customization.
■ Details of the Issue
When “Register to kintone App” was executed while the issue was occurring, a customization file was created in a state where the correct license check could not be performed.