Skip to main content Skip to page footer

Retention of conversations

Conversations are cleaned up in two stages:

  1. Marked as deleted: conversations whose last activity is older than chatSessionLifetimeDays (default 20 days). The record stays for the time being.
  2. Deleted permanently: after another seven days, together with the messages, the change log and the attachments, provided these are still in the “cheddi” folder and are not used anywhere else.

The grace period of seven days is fixed, only the first stage is configurable.

The clean-up command

The clean-up does not happen on its own, it needs a regular run. You can call the command below from the console or register it in the scheduler as a recurring task. A daily run is recommended.

Cleaning up conversations

vendor/bin/typo3 cheddi:auto-delete-sessions

Logs

ChEddi writes two logs:

  • var/log/cheddi_warnings.log for warnings and errors. Always active.
  • var/log/cheddi.log for the verbose trace: chosen model, offered and called tools, charged credits. Controlled through chatLogVerbose, by default it follows the mcpLogVerbose setting of AI Suite MCP.

In both, bearer tokens, long hex hashes and email addresses are redacted automatically, as are the patterns from the MCP configuration and your own from chatLogRedactionPatterns. Switch the verbose trace off in production once monitoring is in place.

Environment report

Since version 0.3.0 ChEddi reports its state in the status report (System → Reports, TYPO3 14: Administration → Reports) under “ChEddi Environment”. Two things are checked there:

  • ChEddi Attachments. Whether PDF, Word and spreadsheet attachments can be read. If a prerequisite is missing, the report names the affected file types and the reason. You can still attach such files, but ChEddi cannot get at their text. In classic mode the libraries ship with the extension, but required PHP extensions have to be installed on the server.
  • ChEddi Request Duration. A turn waits up to 180 seconds for the AI Suite server. If max_execution_time is lower, long turns end in an error. In that case raise the PHP value and the matching web server and proxy timeouts to at least 180 seconds. The report itself cannot see the web server and proxy timeouts.
  • Show larger version Status report with the section ChEddi Environment

    In the status report, the section “ChEddi Environment” checks whether attachments can be read and whether PHP allows enough run time for a chat answer.