Campaign cache not reflecting updates

[1v4n4]

Context:

We fetch some sync-related variables from the campaign config using:

const camp = await this.campaign(message.campaign)

To improve performance, the campaign is cached so we don’t fetch it for every action.

Problem:

The cache is not invalidated or refreshed after a campaign is updated.
This means that if a user modifies campaign settings after the first action is taken, the updated values, in most cases, will not be respected.

Expected behavior:

When a campaign is updated, we should clear the cached value and refetch it to ensure the latest configuration is used.

Solution:

At the CRM level, listen for a campaign_updated event.
When that event is received, clear the campaign cache and refetch the campaign on the next access.
(Note: We need custom events activated on an org level.)

---

Possible larger issue: For a certain type of confirmation (e.g., a client-side action confirmation used in activecampaign.ts), events are going to the deliver queue, and we are taking actions from confirm.supporter

The case where the campaign update is somewhat solved (hack): cleverreach.ts.

[tttp]

Possible larger issue: For a certain type of confirmation (e.g., a client-side action confirmation used in activecampaign.ts), events are going to the deliver queue, and we are taking actions from confirm.supporter

I'm not sure what the issue is, the confirm.supporter queue is used to confirm the supporters and it shouldn't be used for opted-in actions

if you want to process both, you can redirect both to the same queue in rabbitmq?

[1v4n4]

Ahh, redirection should fix it. Thanks!

To try to clarify the two queues case: if we have confirmation on the client's side, we take unconfirmed actions from confirm. supporter queue, not from the delivery queue, which is the case when we sent already confirmed actions (no matter if they are opt-ins or not). And campaign_updated event always goes to the delivery queue