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

Record log does not list correct starting before elements #9656

Closed
remcowesterhoud opened this issue Jun 30, 2022 · 0 comments · Fixed by #9671
Closed

Record log does not list correct starting before elements #9656

remcowesterhoud opened this issue Jun 30, 2022 · 0 comments · Fixed by #9671
Assignees
Labels
kind/bug Categorizes an issue or PR as a bug severity/low Marks a bug as having little to no noticeable impact for the user version:8.1.0-alpha4 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0

Comments

@remcowesterhoud
Copy link
Contributor

remcowesterhoud commented Jun 30, 2022

Describe the bug

In the PROC_INST_CREATION record we will log the elements which the process started at. If a process starts at 2 different element this record will log the same id twice, instead of logging both ids.

To Reproduce

Create a process instance. Start it at 2 different elements. When you look at the creation record it will say it started at the same element twice.

Expected behavior

The records logs shows the correct elements that were started at.

Log/Stacktrace

C PROC_INST_CREATION CREATE         - #006->  -1   -1 - new <process "process_id_27"> (starting before elements: fork_id_18, fork_id_18)  with variables: {boundary_timer_id_25=PT8760H, boundary_timer_id_23=PT8760H, correlationKey=default_correlation_key}
...
C PROC_INST          ACTIVATE       - #012->#006 K008 - RECEIVE_TASK "id_16" in <process "process_id_27"[K004]>
C PROC_INST          ACTIVATE       - #013->#006 K009 - PARALLEL_GATEWAY "fork_id_18" in <process "process_id_27"[K004]>
E PROC_INST_CREATION CREATED        - #014->#006 K010 - new <process "process_id_27"> (starting before elements: fork_id_18, fork_id_18)  with variables: {boundary_timer_id_25=PT8760H, boundary_timer_id_23=PT8760H, correlationKey=default_correlation_key}

This shows we started at fork_id_18 twice, but when looking at the activate commands we can see that we actually started at fork_id_18 and id_16

Environment:

  • OS:
  • Zeebe Version:
  • Configuration:

\cc @korthout

@remcowesterhoud remcowesterhoud added kind/bug Categorizes an issue or PR as a bug team/process-automation labels Jun 30, 2022
@korthout korthout added the severity/low Marks a bug as having little to no noticeable impact for the user label Jun 30, 2022
@korthout korthout self-assigned this Jul 1, 2022
@ghost ghost closed this as completed in 5874c32 Jul 4, 2022
@Zelldon Zelldon added the version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0 label Oct 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes an issue or PR as a bug severity/low Marks a bug as having little to no noticeable impact for the user version:8.1.0-alpha4 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants