Improve service connection error message with connection ID#5467
Open
Improve service connection error message with connection ID#5467
Conversation
- Add new ServiceConnectionNotDeclared localization key - Update error message to include the service connection ID - Add localization for all supported languages (10 languages) - Add test case for service connection not declared scenario - Keep existing test for invalid endpoint ID format
…an up project file by removing unused localization strings
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
tarunramsinghani
approved these changes
Feb 3, 2026
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
We have misleading error message in case that service endpoint is not found while evaluating task.setendpoint command. It shares same message with parsing error and user is not aware what the issue is.
With new error message it should be clearer to the user what is the problem and he can seek more info in public docs.
Description
Changed error message for the case when endpoint not found by provided id during
task.setendpointcommand.Risk Assessment (Low / Medium / High)
Low. Just error message changed.
Unit Tests Added or Updated (Yes / No)
Yes.
Additional Testing Performed
No.
Change Behind Feature Flag (Yes / No)
No.
Tech Design / Approach
Documentation Changes Required (Yes/No)
No.
Logging Added/Updated (Yes/No)
Yes, updated error message used in logs.
No sensitive data logged.
Telemetry Added/Updated (Yes/No)
No.
Rollback Scenario and Process (Yes/No)
Dependency Impact Assessed and Regression Tested (Yes/No)
No changes in dependencies.