docs: Improve task previousTrace documentation (#6538)

---------

Signed-off-by: Rashmi Naidu <[email protected]>
Signed-off-by: Chris Hakkaart <[email protected]>
Signed-off-by: Ben Sherman <[email protected]>

Author: rnaidu

docs/process.md

@@ -1338,7 +1338,11 @@ process hello {
 }
 ```
 
-In the above example, the {ref}`process-memory` is set according to previous trace record metrics. In the first attempt, when no trace metrics are available, it is set to 1 GB. In each subsequent attempt, the requested memory is doubled. See {ref}`trace-report` for more information about trace records.
+In the above example, the {ref}`process-memory` is set according to previous trace record metrics. In the first attempt, when no trace metrics are available, it is set to 1 GB. In each subsequent attempt, the requested memory is doubled. 
+
+:::{note}
+Many fields from the previous task attempts are accessible. See {ref}`trace-report` for a list of available fields.
+:::
 
 ### Dynamic retry with backoff
 

docs/reference/process.md

@@ -37,7 +37,12 @@ The following task properties are defined in the process body:
 : :::{versionadded} 24.10.0
   :::
 : The trace record associated with the previous task attempt.
-: Since the trace record is available after a failed task attempt, it can only be accessed when retrying a failed task execution, i.e., when `task.attempt` is greater than 1.
+: Since the trace record is available after a failed task attempt, it can only be accessed when retrying a failed task execution, i.e., when `task.attempt` is greater than 1. See {ref}`trace-report` for a list of available fields.
+
+: :::{note}
+  The trace fields `%cpu` and `%mem` can be accessed as `pcpu` and `pmem`, respectively.
+  :::
+
 
 `task.process`
 : The name of the process that spawned the task.