Status displayed incorrectly as "succeeded" instead of "started"

[NikolayMetchev]

I have used the plugin to send a slack message when a Build Configuration is started and succeeded. Sometimes the slack message displays the status of the Build Configuration as "succeeded" instead of "started" on the first message and then again when it actually succeeds.

[alexkvak]

So strange. Could you provide some details? E.g. messages screenshots

[NikolayMetchev]

[NikolayMetchev]

[NikolayMetchev]

Do you need more details?

[NikolayMetchev]

Any chance this could be looked at?

[alexkvak]

According to your screenshot I guess the build lasts about 5 minutes? Or not?

[NikolayMetchev]

That particular build yes. We have this configured on other builds as well.

[alexkvak]

So you become notification that build is succeeded when build is only actually started?

[NikolayMetchev]

Yes

[MSupragonas]

I notice similar issue, yet my problem was that TC starts build with branch name 'default' and only after a few seconds, a normal name 'master' is displayed, so a trigger for build start didn't event got invoked. Solved by filtering branch '.'

Also noticed exactly this issue, started two builds with the same settings, one said: started, other successful. Builds had same dependency.

[shachar-ash]

So you become notification that build is succeeded when build is only actually started?

We also encounter the same problem sporadically.

[ofirnn]

We're facing it as well -mostly on jobs that run in high frequency.

[shachar-ash]

Hey @alexkvak, hope you are doing well.
Any news about this one?

[asafsarid]

@alexkvak any updates? Happens here as well.

[alexkvak]

@asafsarid do you have an exactly case to reproduce?

[asafsarid]

@alexkvak thanks for responding.
Actually, we are not sure how to reproduce this since it happens sporadically.
As @ofirnn mentioned, seems that it happens mostly on jobs that run in high frequency.

[shachar-ash]

@alexkvak We still experience this.