A SaaS-hosted Cloud environment is running out of database storage, and IFS Support has identified the `ACT_HI_VARINST` table (tied to the Camunda/BPA workflow engine) and its indexes as the cause — how is this managed or purged?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This table records BPA/workflow execution history, and unbounded growth here has been a confirmed, significant real-world disk-space issue — IFS has shipped a fix (in a specific Support Update within the 23R1 track) that stops recording history into this table and truncates it, reclaiming a substantial amount of database storage in confirmed cases. If you're hitting this, raise it with IFS Support to confirm whether your current release/SU already includes that fix rather than trying to purge the table yourself, since the safe purge/stop-recording behavior needs to come from the platform's own fix rather than a manual DELETE against a Camunda-internal table.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions