You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to run asynchronous tasks via Add-PodeTask followed by Invoke-PodeTask. While Invoke-PodeTask successfully returns a detailed hashtable of task information immediately after invocation, I encounter difficulties accessing similar detailed information later on, especially through RESTful API endpoints. The detailed information includes properties like ID, CompletedTime, Task, Runspace, Timeout, ExpireTime, and Result. This limitation hinders my ability to monitor and manage asynchronous tasks effectively in a production environment.
Steps to Reproduce (complete sample attached)
Setup a Pode server and define an endpoint to initiate an asynchronous task using Add-PodeTask and Invoke-PodeTask.
Invoke the task through the defined endpoint and capture the detailed task information returned by Invoke-PodeTask.
Attempt to retrieve similar task information at a later time or via a different endpoint (e.g., /api/task/:taskId).
Expected Behavior
I expect to be able to retrieve comprehensive task information (similar to what Invoke-PodeTask returns immediately after task invocation) at any point during the task's lifecycle, including after its completion, via RESTful API endpoints or other Pode functions.
Actual Behavior
Post-execution, I am only able to determine if the task is running or not. Detailed information about the task, like what is available immediately after using Invoke-PodeTask, is not accessible through RESTful API endpoints or subsequent queries.
There is also an issue with Test-PodeTaskCompleted that always returns False
Description
I want to run asynchronous tasks via
Add-PodeTask
followed byInvoke-PodeTask
. WhileInvoke-PodeTask
successfully returns a detailed hashtable of task information immediately after invocation, I encounter difficulties accessing similar detailed information later on, especially through RESTful API endpoints. The detailed information includes properties like ID, CompletedTime, Task, Runspace, Timeout, ExpireTime, and Result. This limitation hinders my ability to monitor and manage asynchronous tasks effectively in a production environment.Steps to Reproduce (complete sample attached)
Expected Behavior
I expect to be able to retrieve comprehensive task information (similar to what
Invoke-PodeTask
returns immediately after task invocation) at any point during the task's lifecycle, including after its completion, via RESTful API endpoints or other Pode functions.Actual Behavior
Post-execution, I am only able to determine if the task is running or not. Detailed information about the task, like what is available immediately after using
Invoke-PodeTask
, is not accessible through RESTful API endpoints or subsequent queries.There is also an issue with
Test-PodeTaskCompleted
that always returns FalseThe text was updated successfully, but these errors were encountered: