Unless I am misunderstanding what you are trying to show here?
I had the feeling that in the past all ActionGroups had stopped and turned red as soon as an action failed underneath.
That’s right, just got the old FB7 out again and it was like that there.
I had never paid much attention to it before, but since I am currently revising our FB script, it had seemed strange to me, because I had the feeling that the behavior was different before,
but it only looked like this in two of our three central locations, since there happens to be an AsyncActionGroup being used.
First Error is ignored by ActionGroup, but it doesn’t happen with the second error.
This different behavior is a little bit confusing.
I would have expected that only the last raise would stop everything.
With the AsyncActionGroup errors are displayed in subordinate actions and “Ignore Failure” of the group ignores everything.
With the normal ActionGroup, and everything else, it only affects the actions themselves.
That explains why in some places the “Ignore Failure” in an ActionGroup doesn’t work as we expected.
For years we have had the problem that the FB script runs through in some projects because of “Ignore Failure” in the AsyncActionGroup,
shows “Build Successful” with the green check sign at the end, and the Error = 1 and Ignored = 1 are not seen.
Even with an error, few actions must currently be carried out, e.g. to start Delphi.
I’m trying to remove most of the “Ignore Failure”, but which would be easier if the OnFailure still existed.
Actually, it would not be necessary to ignore errors and then copy files, but it will take some time until these structural problems in our directory structure are fixed.