Environment

Fortify products.

Issue

The following error messages appear when running an Azure DevOps pipeline that includes jobs executed with pre-defined Fortify tasks. These errors occur after a certain period of time, with no log evidence explaining the cause

2024-10-17T06:40:32.8627076Z ##[error]The Operation will be canceled. The next steps may not contain expected logs.
2024-10-17T06:40:32.8803422Z Processing /home/devops_user_01/myagent/_work/17
2024-10-17T06:40:32.8981645Z ##[error]The operation was canceled.
2024-10-17T06:40:32.8988323Z ##[section]Finishing: FortifySCA

Root Cause

The job was likely canceled due to time restrictions on the agent.

According to Azure DevOps documentation, setting a timeout for a job can help avoid wasting resources when a job becomes unresponsive or takes too long. You can configure a job timeout to specify the maximum duration (in minutes) for the job to run.

By default:

• Self-hosted agents can run jobs indefinitely when the timeout is set to 0.
• Microsoft-hosted agents:
  • Public project/repository: Max 360 minutes (6 hours).
  • Private project/repository: Max 60 minutes (unless additional capacity is purchased).

The timeout begins once the job starts running and does not include the time spent in the queue or waiting for an agent.

See full knowledge document here