When are you notified about Script code errors while using Apex Tasks?

When using Apex Tasks in Copado, you receive notifications about script code errors after the deployment is executed. This means that any errors in the Apex code will be captured and reported only once the deployment process has been completed.

The rationale behind this timing is that the deployment occurs in a sequential manner, and script codes are evaluated during this process. If there are any issues in the Apex code, those will be identified and logged as part of the deployment feedback mechanisms within the platform. This allows developers to review and correct errors based on the deployment results rather than just the task execution.

The other options do not align with how errors are reported. For instance, you will not receive immediate notifications upon executing the task because the actual deployment and error-checking occurs after the deployment phase. Errors are also not reported before the deployment starts or merely after reviewing deployment logs, as these would not provide real-time insights on errors pertaining specifically to Apex tasks in the deployment context. Thus, understanding that errors arise post-deployment aligns with how Copado manages and reports on Apex Task executions.