From around 1:00 PM on May 6, 2026, to around 4:00 PM on May 15, 2026, there was an issue with notifications when jobs crashed in gusuku Customine Job Runner.
We sincerely apologize for any inconvenience this may have caused to our users.
■ Date and Time of Occurrence
From around 1:00 PM on May 6, 2026, to around 4:00 PM on May 15, 2026
■ Details of the Issue
When a “scheduled task” or “kintone app webhook” created in Job Runner crashed, all execution history entries were judged and recorded as “Unexpected Error.”
In addition, error notification emails were not sent.
This issue did not affect customer environments, including app slot consumption.
■ Cause
The issue occurred because there was a change in the notification content sent by the infrastructure provider when a timeout or crash occurred.
A similar issue occurred in November 2025. At that time, we believed we had addressed the issue so that no problems would occur even when new and old environments coexisted. However, the cause of this incident was that the old environment had not been fully supported.
次の場所のその他のトピック：
Maintenance and incident announcement / 障害・メンテナンス情報
[R3] Support
平素はgusuku Customineをご利用いただき、誠にありがとうございます。
2026年5月6日午後1時頃から15日午後16時頃まで、gusuku Customine Job Runnerのジョブクラッシュ時の通知に問題が発生しておりました。
ご利用中のユーザー様には、ご不便をお掛けしましたことをお詫び申し上げます。
■ 発生日時
2026年5月6日午後1時頃から15日午後16時頃まで
■ 障害の内容
Job Runnerで作成した「定期実行タスク」「kintoneアプリのWebhook」がメモリ不足でクラッシュした場合の実行履歴がすべて「Unexpected Error.」として判定・記録されておりました。
また、エラー通知メールも送信されておりませんでした。
本障害による、お客様環境へのアプリスロット消費量などへの影響はございません。
■ 発生原因
利用インフラ側のタイムアウト及びクラッシュ時の通知内容に変更があったため。
2025年11月 に同様の障害がありましたが、この際に新/旧の環境が混在していても問題ないように対処したはずでしたが、旧環境には完全に対応できていなかったことが原因となります。
Thank you for using gusuku Customine.
From around 1:00 PM on May 6, 2026, to around 4:00 PM on May 15, 2026, there was an issue with notifications when jobs crashed in gusuku Customine Job Runner.
We sincerely apologize for any inconvenience this may have caused to our users.
■ Date and Time of Occurrence
From around 1:00 PM on May 6, 2026, to around 4:00 PM on May 15, 2026
■ Details of the Issue
When a “scheduled task” or “kintone app webhook” created in Job Runner crashed, all execution history entries were judged and recorded as “Unexpected Error.”
In addition, error notification emails were not sent.
This issue did not affect customer environments, including app slot consumption.
■ Cause
The issue occurred because there was a change in the notification content sent by the infrastructure provider when a timeout or crash occurred.
A similar issue occurred in November 2025. At that time, we believed we had addressed the issue so that no problems would occur even when new and old environments coexisted. However, the cause of this incident was that the old environment had not been fully supported.