feat(api): invalidate stale workflows

[djabarovgeorge]

What changed? Why was the change needed?

Screenshots

Expand for optional sections

Related enterprise PR

Special notes for your reviewer

[SokratisVidros]

The update-workflow.command that is handling existing workflows already invalidates the cache for both keys - See here.

I suggest we apply a more surgical solution to avoid fetching working multiple times from the database that adds extra DB requests.

[djabarovgeorge]

You make a good point. The data that gets validated on updates should indeed be part of what we check.

To illustrate today's issue, here’s the scenario we need to address:

1. A trigger is sent to a non-existent workflow with ID "best-workflow." On the trigger, we try to fetch the workflow, but since it doesn’t exist, we store null in the cache.
2. We then sync "best-workflow."
3. When we trigger "best-workflow" again, we pull the null value from the cache.

To resolve this, we could prevent null from being cached on creation.

While reviewing the issue, I thought we had another problem, but I realized it's not a bug—just an instance of stale memory that we could release. Now, I’m considering removing the extra cache invalidation step and relying on the TTL to clear it, which would simplify the logic and reduce the load on Redis.

What do you think?

[netlify]

✅ Deploy Preview for novu-stg-vite-dashboard-poc ready!

Name	Link
🔨 Latest commit	3c4ff0b
🔍 Latest deploy log	https://app.netlify.com/sites/novu-stg-vite-dashboard-poc/deploys/67322ca10349b100082d4124
😎 Deploy Preview	https://deploy-preview-6887--novu-stg-vite-dashboard-poc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[SokratisVidros]

This invalidation should be added in the delete-workflow usecase. The cache clearance should applies every time a workflow is deleted, not only via sync.

[SokratisVidros]

Moreover, the delete-workflow use case needs to delete from the preferences collection all entries of type WORKFLOW_RESOURCE by _environmentId and workflow internal id. This is irrelevant to this bug, but as I reviewed the code, it's an omission we can easily tackle.

[djabarovgeorge]

Done.
I deleted the old bridge.deleteWorkflow so we could reuse one reusable delete workflow from app-gen.

[SokratisVidros]

Great clean up @djabarovgeorge 👏 👏 👏