Skip to content
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

Functions put all and context do not propagate errors to the result #446

Closed
pihme opened this issue Jun 30, 2022 · 2 comments
Closed

Functions put all and context do not propagate errors to the result #446

pihme opened this issue Jun 30, 2022 · 2 comments
Labels
scope: Camunda 8 Required in the context of Camunda 8 type: bug

Comments

@pihme
Copy link

pihme commented Jun 30, 2022

Describe the bug
Currently the built-in functions put all and context do not propagate errors that are passed in as argument. Instead, they return null in these cases and the error gets lost.

This is the root cause for: camunda/camunda#9543

To Reproduce
see ticket linked above

Expected behavior

  • If an error is passed in, this error should be returned as the result of the function
  • If multiple errors are passed in, the first error should be returned as the result of the function

Environment

@pihme pihme mentioned this issue Jun 30, 2022
Closed
@saig0 saig0 added the scope: Camunda 8 Required in the context of Camunda 8 label Jul 1, 2022
@pihme
Copy link
Author

pihme commented Jul 1, 2022

Implementation was started in branch 446-propagate...

It is currently blocked by

@saig0
Copy link
Member

saig0 commented Jun 1, 2023

We will not work on this issue. Instead, we will look at the topic when implementing custom error handling.
The goal would be that the function returns null and reports an error.

@saig0 saig0 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: Camunda 8 Required in the context of Camunda 8 type: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants