Increasing the length of a description field for an APIM operation causes a time out in the related MCP.

Open
#50 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
openapi
Domain
api

Research direction

Reproduce the APIM operation flow with a description under 1000 characters, create the MCP, then expand the description and observe the timeout. Compare the initial MCP creation path with the later update path; done means the update no longer times out or fails unexpectedly when the description exceeds 1000 characters.

Written by the indexing model from the issue text.

Description

When the  Open API description of an operation is larger than 1000 characters, the MCP creation fails, that's ok. But if you create the service with less than 1000 characters, the MCP is created, later, you can add more than 1000 characters and then the MCP times-out.

Dominant language
No language data
Stars
28
Forks
77
Avg merge
7d 12h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/MCP

All issues in Azure/MCP

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.