-
Notifications
You must be signed in to change notification settings - Fork 748
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
Trigger's default parameter value not being applied #1238
Comments
Thanks! |
@whynowy We deployed the fix (1.4.0), and we are still experiencing this bug. |
@atombender : Did you figure out any solution to this one ? I have same exact problem..Thanks in advance |
@naveenb30 No, unfortunately it still exists. @whynowy This should be reopened. |
This issue has been automatically marked as stale because it has not had |
@whynowy As far as I know, this is still a problem. |
I have a sensor with two dependencies in an
||
. When one dependency triggers, I want to ensure that the other dependency's parameter has a default value.Here's my sensor, simplified:
If the sensor triggers on
dep1
ordep2
, thedataKey
is successfully extracted and stored in the right workflow parameter. However, the other parameter becomes empty, despite the fact that there is avalue
set on thesrc
.As you can see, I also tried providing a default value in the workflow's
parameters
, but the value still becomes empty.Looking at the documentation, there's a discrepancy between the API docs and the guide. The API docs say (my emphasis):
The parameterization tutorial, on the other hand, suggests that
value
is used as a default value if thedataKey
data is missing.There's nothing in the sensor log about failing to read the event data, even though the code (from what I can read here) should complain.
This leads me to think that maybe the dependency data logic isn't executed if the dependency didn't trigger. In other words, with a conditions list like
dep1 || dep2
, then ifdep1
triggers, the parameter section fordep2
is ignored and no value is set. However, it looks likeResolveParamValue()
will not resolve anything if the event does not contain all dependencies.Using 1.2.0. I don't see anything relevant in the git log since then.Version 1.3.1.The text was updated successfully, but these errors were encountered: