New Error without changing code Bad response when Updating work item - 400 - response body: VS403354: Index out of range for path /relations/7

General Questions
,
1

Hello,

All of the sudden im getting this error on several tickets and the code was not changed…

com.exalate.api.exception.IssueTrackerException: Bad response when Updating work item - 400 - response body: VS403354: Index out of range for path /relations/7 at azurenode.services.node.client.AzureClient.filterResponse(AzureClient.scala:815) at azurenode.services.node.client.AzureClient.$anonfun$updateWorkItem$4(AzureClient.scala:466) at scala.concurrent.impl.Promise$Transformation.run(Promise.scala:470) at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:63) at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:100) at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18) at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:94) at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:100) at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:49) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:48) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) at

2

The only thing that was updated was that we added a new Status to our Jira workflow, but this is not used by exalate. Could this be causing the issue and how can we fix it ?

3

I recreated the connection and its giving me this same error on other tickets now. So not sure what is the reason for this issue

4

Hi @Lautaro

are you still facing the same error?

Thanks,

Sonal

5

Yes, i randomly get some tickets with this error, all the previous ones resolve on its own and now i have one that wont go away.

Bad response when Updating work item - 400 - response body: VS403354: Index out of range for path /relations/19

6

Hello Team,

Im still getting this error:

Error Detail Message:

Bad response when Updating work item - 400 - response body: VS403354: Index out of range for path /relations/16

com.exalate.api.exception.IssueTrackerException: Bad response when Updating work item - 400 - response body: VS403354: Index out of range for path /relations/16 at azurenode.services.node.client.AzureClient.filterResponse(AzureClient.scala:815) at azurenode.services.node.client.AzureClient.$anonfun$updateWorkItem$4(AzureClient.scala:466) at scala.concurrent.impl.Promise$Transformation.run(Promise.scala:470) at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:63) at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:100) at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18) at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:94) at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:100) at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:49) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:48) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)

On several tickets, not sure where this is coming from. Cant seem to find any explanation.

Thanks

7

hey @Lautaro

I will update you for this by end of the day today

Thanks,

Sonal

8

Hello Sonal,

Were you able to check on this? Im still getting them randonmly on some tickets, the workaround ive found is to unexalate the broken connection and manually connect it again without setting the option for sync in that moment. Today i had 7 connections broken.

thanks

9

Hi @Lautaro

Can you please check your inbox , i asked you few things regarding the logs?

Kindly validate and confirm.

Waiting for your update!

Thanks,

Sonal

10

Hi @Lautaro

This could be the reason of failure, lets say you have links synchronised from Jira to ADO. Now there could be any update happened in Jira but before that update perform on ADO side, someone deleted the link from ADO work Item.

Can you please confirm whether this is happening at your side ?

Also if this is not the case with you , to debug further we need to analyse the logs so can you please create the ticket in our support portal:

Thanks,

Sonal

11

@Lautaro

I can see you raised the support ticket:

and our support team is helping you.

Thanks,

Sonal