mirror of
https://github.com/n8n-io/n8n.git
synced 2025-01-26 12:01:16 -08:00
46dd4d3105
I have observed that the next hard deletion timeout is not scheduled if the `hardDeleteOnPruningCycle` function throws when fetching the data from the database. That is because the thrown error is not caught and the `scheduleHardDeletion` method is not called. This PR moves the call to `scheduleHardDeletion` into the `scheduleHardDeletion` for better cohesion, and ensures that it is called even if `hardDeleteOnPruningCycle` throws. |
||
---|---|---|
.. | ||
@n8n | ||
@n8n_io/eslint-config | ||
cli | ||
core | ||
design-system | ||
editor-ui | ||
node-dev | ||
nodes-base | ||
workflow |