Skip to content

What to do when in case of gradual Rollout with Socket Mode Backends #1808

@vedanta28

Description

@vedanta28

We are currently migrating our Slack bot from an older architecture (V1) to a new one (V2). During this "cut over" phase, we have both backends running concurrently. Both backends use the same Bot Token (xoxb-) but different App Token. Now, events are being distributed randomly between V1 and V2. This is an issue for us.

I found it in the slack documentation that:

When multiple connections are active, each payload may be sent to any of the connections. It's best not to assume any particular pattern for how payloads will be distributed across multiple open connections.

Now, is there any way to handle a gradual rollout in such cases, except say having to setup some kind of proxy setup which does this routing for us?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions