Sub action status API results

Usage and Config
1

When we push a multiple action group with the 2 components (one relevant, one not relevant), the overall status result from the API comes back as Completed, which is correct because at least one component completed successfully. However, there is no sub action status of “not relevant” for the 2nd component.

I have other multiple action group examples where there is a subaction status of “not relevant” returned of non-relevant components.

Is there any rhyme or reason why some have a sub action status of not relevant vs others? maybe task vs fixlet?

2

Hi, can anyone help with this?
thanks

3

Can you provide the API call you are using and the results?

4

Hi, the question is why does the response have no action details for action ID 534602 even though it did run the Multiple Action Group to completion?. We know that the fixlet under actionID 534602 is not relevant, but we are expecting an action result that says it is not relevant.

We do see other action examples where the action status does say ‘not relevant’, but there must be something unique about this one.

POST input:

<?xml version="1.0" encoding="UTF-8"?>
<BES
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="BES.xsd">
    <MultipleActionGroup>
        <Title>job123</Title>
        <Relevance>true</Relevance>
        <SourcedMemberAction>
            <SourceFixlet>
                <Sitename>CustomSite1</Sitename>
                <FixletID>289132</FixletID>
                <Action>Action1</Action>
            </SourceFixlet>
        </SourcedMemberAction>
        <SourcedMemberAction>
            <SourceFixlet>
                <Sitename>CustomSite2</Sitename>
                <FixletID>514168</FixletID>
                <Action>Action1</Action>
            </SourceFixlet>
        </SourcedMemberAction>
        <Settings>
            <ContinueOnErrors>true</ContinueOnErrors>
        </Settings>
        <Target>
            <ComputerID>3010208</ComputerID>
        </Target>
    </MultipleActionGroup>
</BES>

Response:

<BESAPI xsi:noNamespaceSchemaLocation="BESAPI.xsd">
    <ActionResults Resource="https://redacted:52311/api/action/534600/status">
        <ActionID>534600</ActionID>
        <Status>Open</Status>
        <DateIssued>Tue, 26 May 2020 17:39:04 +0000</DateIssued>
        <Computer ID="3010208" Name="server1">
            <Status>The action executed successfully.</Status>
            <State IsError="0">3</State>
            <ApplyCount>1</ApplyCount>
            <RetryCount>1</RetryCount>
            <LineNumber>3</LineNumber>
            <StartTime>Tue, 26 May 2020 17:39:10 +0000</StartTime>
            <EndTime>Tue, 26 May 2020 17:39:10 +0000</EndTime>
        </Computer>
        <MemberActionResult Resource="https://redacted:52311/api/action/534601/status">
            <ActionID>534601</ActionID>
            <Computer ID="3010208" Name="server1">
                <Status>The action executed successfully.</Status>
                <State IsError="0">3</State>
                <ExitCode>0</ExitCode>
                <ApplyCount>1</ApplyCount>
                <RetryCount>1</RetryCount>
                <LineNumber>23</LineNumber>
                <StartTime>Tue, 26 May 2020 17:39:10 +0000</StartTime>
                <EndTime>Tue, 26 May 2020 17:39:10 +0000</EndTime>
            </Computer>
        </MemberActionResult>
        <MemberActionResult Resource="https://redacted:52311/api/action/534602/status">
            <ActionID>534602</ActionID>
        </MemberActionResult>
    </ActionResults>
</BESAPI>