We have many custom TFS tasks.
Sometimes, when the user opens the release definition or release definition, the user will be prompted “Task not found”, as shown below.
We assume that the user clicks “OK”.
Then there is a danger Choose’Save’ it. Saving it will delete the task, and it is not easy to restore the definition with the history record.
I would like to know why this prompt appears.
Then check whether these custom tasks are also missing in the task list and the corresponding build definition.
One possibility, if your custom task is calling the TFS API, you must specify the api-version parameter in it. You may still be using the wrong version value. It will only be installed in TFS when you upgrade the TFS version/update Update the API version on .When you use TFS 2017 Update 1, you may not be able to use a specific version of the API in TFS 2017 Update 3.
For example, if your task uses an older version of the REST API. For compatibility, definition elements that are not supported by the rest client version will be removed before the definition is sent to the client. Unfortunately, if the client then saves the definition, the aspects that are not supported by its api version are removed from the definition. /p>
You can also create a new version definition for testing, and then add tasks that are the same as the old version definitions to see if the problem still exists. This will narrow the problem to the task itself or just some caching. For caching issues, please Refresh it as suggested by Pranay.
We are TFS 2017 Update 3. After upgrading from TFS 2017 Update 1, this problem started to appear.
< p>we There are many custom TFS tasks.
Sometimes, when the user opens the release definition or release definition, the user will be prompted “Task not found”, as shown below.
We assume that the user clicks “OK”.
Then there is a dangerous option to’save’ it. Saving it will delete the task, and it is not easy to restore the definition with history.
I would like to know why this prompt appears.
p>
If there are accidental edits, it is recommended that you first check the history of the release definition. If something causes the definition to be changed, it should be displayed as an update and may provide Some clues about why these tasks disappeared.
Then check whether these custom tasks are also missing in the task list and the corresponding build definition.
One possibility If your custom task is calling the TFS API, you must specify the api-version parameter in it. You may still be using the wrong version value. The API version will only be updated on the TFS installation when you upgrade the TFS version/update .When you use TFS 2017 Update 1, you may not be able to use a specific version of the API in TFS 2017 Update 3.
For example, if your task uses an older version of the REST API. For compatibility, Before sending the definition to the client, the definition elements that are not supported by the rest client version will be deleted. Unfortunately, if the client then saves the definition, aspects that are not supported by its api version are deleted from the definition.
< p>You can also create a test new version definition, and then add the same task as the old version definition to see if the problem still exists. This will narrow down the problem with the task itself or just some caching. For caching issues, please follow Pranay’s suggestion Refresh it.