HTTP connector type service tasks, history records, process instance records, and task records are not persisted in the database

[KangTomwk]

Environment (Required on creation)

camunda 7.16

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)

创建如下流程图所示

其中自动1、自动2、自动3均为http-connector类型serviceTask任务节点，在流程创建后，执行完成，ACT_HI_TASKINST、ACT_HI_ACTINST等表中未查询到该实例的任何任务，未进行持久化操作，且配置是history-level: audit，是服务任务不支持历史记录入库查询吗？

[joaquinfelici]

Hello @KangTomwk ,

Thanks for reporting this bug. Unfortunately:

• The information you provided is not enough to understand the issue. Please use our issue templates for reporting bugs and fill out all the required fields. If it can help, here's the documentation for history configuration.
• Camunda 7.16 is an old version and out of maintenance.
• Camunda 7 has reached End of Life a few weeks ago. I strongly recommend to check out Camunda 8.

I'll be closing this issue for now, thanks again!

[KangTomwk]

Hello @KangTomwk ,

Thanks for reporting this bug. Unfortunately:

* The information you provided is not enough to understand the issue. Please use our issue templates for reporting bugs and fill out all the required fields. If it can help, here's the [documentation for history configuration](https://docs.camunda.org/manual/7.24/user-guide/process-engine/history/history-configuration/#choose-a-history-level).

* Camunda 7.16 is an old version and out of maintenance.

* Camunda 7 has reached End of Life a few weeks ago. I strongly recommend to check out [Camunda 8](https://github.com/camunda/camunda).

I'll be closing this issue for now, thanks again!

The serviceTask task node is unable to retrieve historical person records as they have not been written into the table，The historical level configuration is audit

[joaquinfelici]

Hello @KangTomwk ,

To answer your question: yes, I confirm that when history is enabled, service tasks information should be stored in the ACT_HI_ACTINST table. Some pointers I can give you:

1. Make sure you're checking the right table and filter, activity type should be serviceTask.
2. Verify that the effective history level is stored in the database (in the ACT_GE_PROPERTY table).
3. Make sure that TTL is not too short and that entries hasn't simply been removed by history cleanup.

However, we don't have enough information to suggest that the behavior you experience is a bug, and as I mentioned above, 7.16 has been out of maintenance for a while. If the issue persists, you can try a more recent version and see if the issue is also there.

As a reminder, Camunda 7 has reached End of Life a few weeks ago. I strongly recommend to check out Camunda 8.

Thank you.