SAP Knowledge Base Article - Preview

3151717 - How to troubleshoot issues where Business Processes and scheduled CronJobs are not triggered

Symptom

This article outlines the basic (but not exhaustive) checks that can be taken to quickly identify issues causing tasks not to execute. It is based on the BufferedAuxTablesTasksProvider Strategy which is used by default as of Commerce version 2005.

<bean id="configurableTasksProvider" class="de.hybris.platform.task.impl.ConfigurableTasksProvider" autowire="constructor">
<constructor-arg ref="bufferedAuxTablesTasksProvider" index="1"/>
</bean>

To confirm if this strategy is used, look for the following entry in the application startup logs:

INFO   | jvm 1    | main    | 2020/09/18 23:00:07.932 | INFO  [Task-master-poll] [ConfigurableTasksProvider] no tasks provider defined - default tasks provider (de.hybris.platform.task.impl.BufferedAuxTablesTasksProvider) will be used

Note: If you see de.hybris.platform.task.impl.DefaultTasksProvider instead, not all steps in this KBA will necessarily apply. For example, the previous strategy did not make use of the tasks_aux_scheduler, tasks_aux_workers and tasks_aux_queue tables. The polling queries can vary as well.


Read more...

Environment

SAP Commerce or SAP Commerce on the Public Cloud.

  • Versions 2005 and over OR
  • Version 1905 with the property: task.polling.provider=bufferedAuxTablesTasksProvider .

Product

SAP Commerce Cloud all versions

Keywords

cronjob, cron job, business process , KBA , CEC-COM-CPS-TSK , Cronjob - Impex - Task Engine , How To

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.