Get-PveNodesTasks

Read task list for one node (finished tasks).

API: GET /nodes/{node}/tasks, Proxmox VE API viewer

Syntax

Get-PveNodesTasks
    [-PveTicket <PveTicket>]
    [-Errors <bool>]
    [-Limit <int>]
    -Node <string>
    [-Since <int>]
    [-Source <string>]
    [-Start <int>]
    [-Statusfilter <string>]
    [-Typefilter <string>]
    [-Until <int>]
    [-Userfilter <string>]
    [-Vmid <int>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Errors	bool	No	Only list tasks with a status of ERROR.
-Limit	int	No	Only list this number of tasks.
-Node	string	Yes	The cluster node name.
-Since	int	No	Only list tasks since this UNIX epoch.
-Source	string	No	List archived, active or all tasks. Values: archive, active, all.
-Start	int	No	List tasks beginning from this offset.
-Statusfilter	string	No	List of Task States that should be returned.
-Typefilter	string	No	Only list tasks of this type (e.g., vzstart, vzdump).
-Until	int	No	Only list tasks until this UNIX epoch.
-Userfilter	string	No	Only list tasks from this user.
-Vmid	int	No	Only list tasks for this VM.

Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.

Output

A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.