Between 2:00 AM on November 5, 2025 and 6:30 PM on November 6, 2025, an issue occurred with notifications for job crashes in gusuku Customine Job Runner.
We sincerely apologize for any inconvenience this may have caused our users.
■ Incident Period
From around 2:00 AM on November 5, 2025 to around 6:30 PM on November 6, 2025
■ Details of the Issue
When jobs created with the Job Runner — such as “Scheduled Tasks” or “kintone App Webhooks” — timed out or crashed, their execution logs were all recorded as “Unexpected Error.” Additionally, error notification emails were not sent during this period.
Please note that this incident did not affect the app slot usage or any other operational aspects in customer environments.
■ Cause of the Issue
The issue was caused by a change in the notification behavior on the infrastructure side when timeouts or crashes occurred.
More topics in
Maintenance and incident announcement / 障害・メンテナンス情報
[R3] Support
平素はgusuku Customineをご利用いただき、誠にありがとうございます。
2025年11月5日午前2時頃から6日午後6時半頃まで、gusuku Customine Job Runnerのジョブクラッシュ時の通知に問題が発生しておりました。
ご利用中のユーザー様には、ご不便をお掛けしましたことをお詫び申し上げます。
■ 発生日時
2025年11月5日午前2時頃から6日午後6時半頃まで
■ 障害の内容
Job Runnerで作成した「定期実行タスク」「kintoneアプリのWebhook」がタイムアウト、もしくはクラッシュした場合の実行履歴がすべて「Unexpected Error.」として判定・記録されておりました。
また、エラー通知メールも送信されておりませんでした。
本障害による、お客様環境へのアプリスロット消費量などへの影響はございません。
■ 発生原因
利用インフラ側のタイムアウト及びクラッシュ時の通知内容に変更があったため。
Thank you for using gusuku Customine.
Between 2:00 AM on November 5, 2025 and 6:30 PM on November 6, 2025, an issue occurred with notifications for job crashes in gusuku Customine Job Runner.
We sincerely apologize for any inconvenience this may have caused our users.
■ Incident Period
From around 2:00 AM on November 5, 2025 to around 6:30 PM on November 6, 2025
■ Details of the Issue
When jobs created with the Job Runner — such as “Scheduled Tasks” or “kintone App Webhooks” — timed out or crashed, their execution logs were all recorded as “Unexpected Error.”
Additionally, error notification emails were not sent during this period.
Please note that this incident did not affect the app slot usage or any other operational aspects in customer environments.
■ Cause of the Issue
The issue was caused by a change in the notification behavior on the infrastructure side when timeouts or crashes occurred.