Question
Accenture Solutions Pvt Ltd
IN
Last activity: 9 May 2025 10:48 EDT
Product bug : Job is executing on selection of trace option in Admin studio.
Job is executing on selection of trace option in Admin studio.:
As per functionality trace option should only trace the events , however the job schedular trace option works differently (which is incorrect) executes the activity defined in job schedular .
- could you let us know if that is defined in that way or issue is product .
if it is defined in such way ... it would have named as trace and run (in earlier version i think we had Trace ,Run, Trace and run ).
Pegasystems Inc.
GB
@ShanmukhG6223 Below is GenAI -researched response. Please check the References carefully:
When you select the trace option for a job in the job scheduler, it is designed to execute the activity defined in the job scheduler while tracing it. This execution is intentional and allows you to analyze the results of tracing for troubleshooting purposes.
You're absolutely correct in your recollection that earlier versions had separate options for "Trace," "Run," and "Trace and run." The current functionality essentially combines these features, but with an important distinction: while the job executes immediately when traced, this execution is not included in the history of Job Run activities. This means the last run activity time and next run activity time are not recalculated.
According to the documentation, this immediate execution behavior is specifically designed for debugging purposes during application development. The documentation states: "For debugging purposes during application development, you can trace job anytime. When you do so, then the Job Run happens immediately but the run is not included in the history of Job Run activities."
References: Tracing a job Admin Studio
@ShanmukhG6223 Below is GenAI -researched response. Please check the References carefully:
When you select the trace option for a job in the job scheduler, it is designed to execute the activity defined in the job scheduler while tracing it. This execution is intentional and allows you to analyze the results of tracing for troubleshooting purposes.
You're absolutely correct in your recollection that earlier versions had separate options for "Trace," "Run," and "Trace and run." The current functionality essentially combines these features, but with an important distinction: while the job executes immediately when traced, this execution is not included in the history of Job Run activities. This means the last run activity time and next run activity time are not recalculated.
According to the documentation, this immediate execution behavior is specifically designed for debugging purposes during application development. The documentation states: "For debugging purposes during application development, you can trace job anytime. When you do so, then the Job Run happens immediately but the run is not included in the history of Job Run activities."
References: Tracing a job Admin Studio
if you believe the product is not working as documented please log a support incident via the MSP. Provide the INC reference here.