Currently, scripts cannot be divided into custom steps directly. Each URL change is recorded as one step. Network Transaction flows consume points based on the number of steps. For example, if a script has ten steps, one complete execution consumes 10 points.The following issues may occur:A. The number of steps may be inconsistent across data points for the same task. B. Except for the first page, other pages may not have web performance data. C. Script password protection may need special handling. D. Transaction processing failures may not be reported directly. Because the script continues waiting for elements, issues eventually result in task timeout. This behavior is expected.