Azure Devops - TF400898

Question

Azure Devops - TF400898

Mike Hudgell 25

When I try and work on a pull request in azure devops, I get error TF400898

503 - Hold please!

Our services are momentarily unavailable. We're working to restore everything as quickly as possible! Check back soon or visit our status page for updates.

23/02/2026 16:36:19 (UTC)

00b1c176-0ac8-4d36-b893-ffeb2687037c

Mike Hudgell 25 Reputation points

2026-02-23T16:56:27.5533333+00:00

What timezoneis that in?

I believe that we're hosted in the uk/eu?
Siddhesh Desai 3,935 Reputation points Microsoft External Staff Moderator

2026-02-23T18:57:36.4933333+00:00

Hi @Mike Hudgell

Can you please provide me the details, I have asked in the Private chat?

It is for US but it's a primary region. Are you still facing the same issue?
Alexander Roth 0 Reputation points

2026-02-24T15:00:16.2166667+00:00

Hi,

we have the same problem.

Its a huge and strange problem.

Some Pull Requests can easily be created - as they can be created normally.

Some Pull Requests can never be created, like a simple branch from one branch to another.

Its always the same kind of message shown
Alexander Roth 0 Reputation points

2026-02-24T15:13:39.64+00:00

Has it something to do with the 400 character limit?

https://learn.microsoft.com/en-us/answers/questions/5378495/utilizing-the-400-character-file-path-limit
Siddhesh Desai 3,935 Reputation points Microsoft External Staff Moderator

2026-03-04T06:20:34.01+00:00

@Alexander Roth

yes, it is very likely related to file path length**, but not to the PR description or title length.**

Azure DevOps allows pushing very long paths, but PR creation uses additional backend services (diff generation, merge simulation, policy evaluation, UI rendering) that still enforce stricter, non-configurable limits. When those limits are exceeded, the service fails with a generic SQL exception instead of a clear message.
Siddhesh Desai 3,935 Reputation points Microsoft External Staff Moderator

2026-03-04T06:21:08.46+00:00

Hi @Mike Hudgell

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

1 answer

Your answer

Mike Hudgell 25 Reputation points

2026-02-23T16:56:27.5533333+00:00

What timezoneis that in?

I believe that we're hosted in the uk/eu?
Siddhesh Desai 3,935 Reputation points Microsoft External Staff Moderator

2026-02-23T18:57:36.4933333+00:00

Hi @Mike Hudgell

Can you please provide me the details, I have asked in the Private chat?

It is for US but it's a primary region. Are you still facing the same issue?
Alexander Roth 0 Reputation points

2026-02-24T15:00:16.2166667+00:00

Hi,

we have the same problem.

Its a huge and strange problem.

Some Pull Requests can easily be created - as they can be created normally.

Some Pull Requests can never be created, like a simple branch from one branch to another.

Its always the same kind of message shown
Alexander Roth 0 Reputation points

2026-02-24T15:13:39.64+00:00

Has it something to do with the 400 character limit?

https://learn.microsoft.com/en-us/answers/questions/5378495/utilizing-the-400-character-file-path-limit
Siddhesh Desai 3,935 Reputation points Microsoft External Staff Moderator

2026-03-04T06:20:34.01+00:00

@Alexander Roth

yes, it is very likely related to file path length**, but not to the PR description or title length.**

Azure DevOps allows pushing very long paths, but PR creation uses additional backend services (diff generation, merge simulation, policy evaluation, UI rendering) that still enforce stricter, non-configurable limits. When those limits are exceeded, the service fails with a generic SQL exception instead of a clear message.
Siddhesh Desai 3,935 Reputation points Microsoft External Staff Moderator

2026-03-04T06:21:08.46+00:00

Hi @Mike Hudgell

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 1

Hi @Mike Hudgell

Thank you for reaching out to Microsoft Q&A.

As confirmed on Private chat the issue is resolved, and it is working now.

There was one incident that was affecting Azure Repos which might have affected your Pull request. And this might have caused a transient issue causing the Pull request to fail.

Refer the Incident here: https://status.dev.azure.com/_event/751923246 which is resolved and the fix is applied.

Hope this helps!

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

Azure Devops - TF400898

1 answer

Your answer