SAP Knowledge Base Article - Preview

3423117 - Cronjob stuck in RUNNING status after pod crash

Symptom

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

The issue could happen when a cronjob status is not correctly reset after a pod crash, e.g. most frequently stuck in "RUNNING" status and cannot be picked up by another node to continue being processed.


Read more...

Environment

SAP Commerce Cloud

Product

SAP Commerce Cloud all versions

Keywords

cron job, stuck , KBA , CEC-SCC-PLA-PL , Platform , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.