Thanks!

Did you try this new view? We read attachments and unfurl_links from this render response here when calling slack, both of them will be nil in this view, i don't know how Slack api deals with nil for both of these. If they don't handle it well, we can set defaults for those two fields.

Oh good to know.

We couldn't figure out getting local APRb to talk to staging Rabbit, so maybe we can try now that all the PRs have been merged to staging.

Careful connecting a local consumer to staging RabbitMQ, as I think there have been problems disconnecting these later on when a real staging consumer wants to step in.

@ashkan18 did I remember this correctly? What's the recommended practice around different environments and their bindings?

yes, basically there are two things we need to do when connecting locally to staging RabbitMQ, we need to first change the queue name locally to something like `"ashkan_local_aprb_#{topic}_queue" here so we don't consume staging events. This then will create a new queue in RabbitMQ staging, the issue is it won't delete the queue once we stop the connection, so we need to manually go to dashboard and delete the queue.

I think there are few options we can use to delete the queue if nothing is connected but that may not make sense for staging/production cases.