"HTTP Status 400 – Bad Request" when clicking on workflows.

Post author
Jean Monlong

When I try to launch a workflow, I get an error which I think is about "data access". It's when I click on a workflow once in the "Workflow" tab.

I get a red popup at the top-right that says "Error loading data". In the details, it says:

{
  "causes": [],
  "exceptionClass": "bio.terra.workspace.client.ApiException",
  "message": "<!doctype html><html lang=\"en\"><head><script src=\"https://us.jsagent.tcell.insight.rapid7.com/tcellagent.min.js\" tcellappid=\"FCProd-EBOgM\" tcellapikey=\"AQQBBAFLGLOxL7VE9IF9ESlLvCxD5Ykr_7xkQKq_rgn_P58IWjOhOzIh6p3aI4pTWaprlUw\" tcellbaseurl=\"https://us.agent.tcell.insight.rapid7.com/api/v1\"></script><title>HTTP Status 400 – Bad Request</title><style type=\"text/css\">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 400 – Bad Request</h1></body></html>",
  "source": "rawls",
  "stackTrace": [
    {
      "className": "bio.terra.workspace.client.ApiClient",
      "fileName": "ApiClient.java",
      "lineNumber": 752,
      "methodName": "invokeAPI"
    },
    {
      "className": "bio.terra.workspace.api.ResourceApi",
      "fileName": "ResourceApi.java",
      "lineNumber": 182,
      "methodName": "enumerateResources"
    },
    {
      "className": "org.broadinstitute.dsde.rawls.dataaccess.workspacemanager.HttpWorkspaceManagerDAO",
      "fileName": "HttpWorkspaceManagerDAO.scala",
      "lineNumber": 142,
      "methodName": "enumerateDataRepoSnapshotReferences"
    },
    {
      "className": "org.broadinstitute.dsde.rawls.snapshot.SnapshotService",
      "fileName": "SnapshotService.scala",
      "lineNumber": 107,
      "methodName": "$anonfun$retrieveSnapshotReferences$1"
    },
    {
      "className": "scala.util.Try$",
      "fileName": "Try.scala",
      "lineNumber": 210,
      "methodName": "apply"
    },
    {
      "className": "org.broadinstitute.dsde.rawls.snapshot.SnapshotService",
      "fileName": "SnapshotService.scala",
      "lineNumber": 107,
      "methodName": "retrieveSnapshotReferences"
    },
    {
      "className": "org.broadinstitute.dsde.rawls.snapshot.SnapshotService",
      "fileName": "SnapshotService.scala",
      "lineNumber": 141,
      "methodName": "$anonfun$enumerateSnapshots$1"
    },
    {
      "className": "scala.concurrent.impl.Promise$Transformation",
      "fileName": "Promise.scala",
      "lineNumber": 467,
      "methodName": "run"
    },
    {
      "className": "java.util.concurrent.ForkJoinTask$RunnableExecuteAction",
      "fileName": null,
      "lineNumber": -1,
      "methodName": "exec"
    },
    {
      "className": "java.util.concurrent.ForkJoinTask",
      "fileName": null,
      "lineNumber": -1,
      "methodName": "doExec"
    },
    {
      "className": "java.util.concurrent.ForkJoinPool$WorkQueue",
      "fileName": null,
      "lineNumber": -1,
      "methodName": "topLevelExec"
    },
    {
      "className": "java.util.concurrent.ForkJoinPool",
      "fileName": null,
      "lineNumber": -1,
      "methodName": "scan"
    },
    {
      "className": "java.util.concurrent.ForkJoinPool",
      "fileName": null,
      "lineNumber": -1,
      "methodName": "runWorker"
    },
    {
      "className": "java.util.concurrent.ForkJoinWorkerThread",
      "fileName": null,
      "lineNumber": -1,
      "methodName": "run"
    }
  ],
  "statusCode": 400
}

I suspect it's something with me because it still works for a colleague, and I get the error for all the workflows I tried and in different workspaces. My permissions and billing projects look fine though.

Anyone has an idea of what could be wrong? Or what I could try?

Thanks, Jean

Comments

2 comments

  • Comment author
    Pamela Bretscher

    Hi Jean,

    Thank you for writing in about this issue! We are actually working with another user who is experiencing this error as well. We are trying to determine the cause of this error and why it is only occurring for some users. I will keep you updated on our investigation of the issue!

    Kind regards,

    Pamela

    0
  • Comment author
    Jean Monlong

    Thanks for looking into this. If there is any way, even a temporary hack, to get around this issue, I would be very interested because it's a real blocker in my work now to not be able to launch any workflows. 

    There is a project in particular that I wish I could work on, so if there is a way to make it work on even just one workspace, that would help me a lot.

    Thanks again,
    Jean

    0

Please sign in to leave a comment.