Project

General

Profile

Actions

Question #17288

closed

The "trigger agent" feature from the webui should not report success when there is failure?

Added by Victor Héry about 4 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - UI & UX
Target version:
Regression:

Description

Hello,

I am a big lover of the new 6.0 feature that allow to trigger the agent from a node in the webui, thanks a lot for this feature!

However, I have noticed that when there is an error, the output still show a green check mark ✅

Here is a screenshot:

I guess it's not really a bug, but I think if the run fails, it could be good to use a red check instead, so the user wnats to click on the "show output" button to see hat is the problem?

It may avoid user thinking the agent has ran where it has not :)

(Just to avoid any misunderstanding, here the agent run failed because the agent is still in 5.0, this is not de point of this ticket ;-) )

Regards,

Actions #1

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version set to 6.0.6

Thanks Victor!

There are some cases where the UI Shows a red cross.

But i think it only look at api response status (which is 200, the api call was 'ok'), but we didn't look into the result (the server calls a command / another api to trigger remote run, and i think something in the middle don't treat it as an error)

Anyway you are right, there should be a red cross!!

Actions #2

Updated by Victor Héry about 4 years ago

Okay, I never have a red cross at the moment (guess I am happy it means everything works :-D)

So in this special case (timeout), I think there is no HTTP code 200, so this is just another case to add in the "red cross list" :-)

Thanks for your answer, you may close if there is no other action

Regards,

Actions #3

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.6 to 6.0.7
Actions #4

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.7 to 6.0.8
Actions #5

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.8 to 6.0.9
Actions #6

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.9 to 6.0.10
Actions #7

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.10 to 798
Actions #8

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 798 to 6.1.14
Actions #9

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #10

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #11

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #12

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #13

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #14

Updated by Alexis Mousset over 2 years ago

  • Status changed from New to Resolved

It is indeed a limitation of the current remote run relay API.

Actions

Also available in: Atom PDF