When using Apex Tasks, when are you notified of any Script code errors?

In the context of using Apex Tasks, notification of Script code errors occurs once the deployment is executed. This is because the deployment process involves the execution of the Apex code within the context of the deployment, allowing any errors that arise during this execution phase to be captured and reported.

When the deployment is carried out, the system evaluates the Script code and can identify any runtime errors that occur, such as improper logic or references to nonexistent variables. This stage is critical, as it simulates the actual execution environment, ensuring that any issues with the Script will be flagged at this point before the final deployment is completed.

While there are mechanisms for checking code validity at earlier points, such as saving the Apex Task or validating the script, these do not catch all possible execution errors because they do not execute the code in the same way that a deployment does. Therefore, the accurate point at which you are informed of Script code errors is during the actual deployment after the execution has taken place.