Can't get this to work outside of BeepBoop

[nbst84]

Can't get this to work outside of BeepBoop

[simonsayscode]

This is probably way too late but a few things:

Assumptions:
That your app is correctly listening to a port, which I guess can be inferred by the fact that your function is hit by Slack events.
That MemoryStore is accessing the memory store file that's in slapp.

Major:
In your context, you never call next() which means that it will just hang in your context and not continue. This follows the express middleware pattern in that you need to explicitly call next(). This explains why your middleware and the subsequent routes aren't hit. Also, since Slack tries to retry several times if it gets no response, this also explains why you get repeated attempts/hits to context.

Minor:
This is probably just a proof of concept but I would recommend not having the db connect done in the context since that function is called on each Slack call. You don't want to have the connect and shutdown each call since that'd be extremely inefficient as opposed to initiating the connect once and having the pool live across the server duration.
You have a typo in reaction_added

[nbst84]

Thank you for your response. I have indeed moved on and implemented directly against the Slack API but hopefully this will be useful information for other people.

Thanks

[mbrevoort]

Thanks @simonsayscode! @nicolasbrigodiot sorry we let this slip by! The key issue was not calling next() in the context function.