[BUG] Unknown TriggeredWebJobStatus value. Parameter name: value Actual value was Aborted / Running.

[ahmedHashwa]

Library name and version

Azure.ResourceManager.AppService 1.0.2

Describe the bug

When using Azure.ResourceManager.AppService library to request the status of Triggered Webjobs in Azure, an exception occurs as it doesn't recognize the status of Aborted and Running.

Expected behavior

To be able to get the current status of the TriggeredWebJob, which may include Pending, Running, Success, Failed, and Aborted

Actual behavior

Exception is thrown.

Reproduction Steps

1- Install the aforementioned Library.
2- Make sure you have an Azure Subscription along with a Triggered WebJob aborted/running.
3- Run the following code replacing items in <> with proper values.

        var client = new ArmClient(new DefaultAzureCredential()); 
        var subscription = await client.GetDefaultSubscriptionAsync();  
        var resourceGroups = subscription.GetResourceGroups();  
        ResourceGroupResource resourceGroup = await resourceGroups.GetAsync(<resourceGroupName>);  
        var website = await resourceGroup.GetWebSiteAsync(<webAppName>);  
        await website.Value.GetWebSiteSlotTriggeredWebJobAsync(<webJobName>);

Environment

Azure AppService

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[HarveyLink]

Hi @ahmedHashwa ,Thank you for using Azure SDK for .NET.
As the service swagger definition, we only have 3 status value, which are: Error/Failed/Success.
If there are other available values, then the service team need to update the definition. You could open an Azure support request to get help on that.
Also, if you could provide us the correct values, we could fix it at SDK side as work around.

[github-actions]

Hi @ahmedHashwa. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[ahmedHashwa]

@HarveyLink
Thank you for your response.
I got the exception for the aforementioned values in TriggeredWebJobStatus:

Aborted
Running

It is also expected to get exceptions if another value is returned, such as:
Initializing: according to Kudu TriggeredJobRunLogger.cs

As mentioned, when I try to get an object representing the job, I get that exception, which prevents me from running it through the API if it is in Aborted Status, for example.

[HarveyLink]

Issue fixed, new package released, please have a try on that.