-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement] Slack intermediate catch event breaks on event subscription #1015
Comments
need to be discussed in Architecture discussion. @igpetrov will share his thoughts in the architecture sync |
With the
Investigating |
9 tasks
Fixed in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
Intermediate catch event fails on the first request (challenge echo) because the proposed
Correlation key (payload)
field, suggested by the doc asrequest.body.event.text
is never present but looks like{"token":"XXX","challenge":"YYY","type":"url_verification"}
thus failing with500
.While this is expected behaviour,
500
is not an option an degrades overall user experience when building an element template with Slack intermediate connector.As a workaround suggested:
if request.body.event = null then "" else request.body.event.text
instead ofrequest.body.event.text
at least until we find a better approach.Steps to Reproduce
Suggested fix
Correlation key (payload)
field with safe values, orEnvironment
The text was updated successfully, but these errors were encountered: