synapse icon indicating copy to clipboard operation
synapse copied to clipboard

Activity does not produce a starting/started event before faulting

Open JBBianchi opened this issue 3 years ago • 1 comments

What happened: On the WebSocket stream, an activity of type action doesn't seem to start, it's faulted and executed directly:

image

(Fault cause: An error occured while evaluting the specified expression: 'jq.exe' is not recognized as an internal or external command,\r\noperable program or batch file.)

What you expected to happen: The activity to be started before being faulted/executed

How to reproduce it: Deploy & run the following workflow:

{
  "id": "order-dog",
  "version": "1.0.0",
  "specVersion": "0.8",
  "name": "Order pet",
  "description": "A workflow used to order a pet on the Swagger pet store",
  "functions": [
    {
      "name": "get-user-by-name",
      "type": "rest",
      "operation": "https://petstore.swagger.io/v2/swagger.json#getUserByName"
    },
    {
      "name": "login-user",
      "type": "rest",
      "operation": "https://petstore.swagger.io/v2/swagger.json#loginUser"
    },
    {
      "name": "get-pets-by-status",
      "type": "rest",
      "operation": "https://petstore.swagger.io/v2/swagger.json#findPetsByStatus"
    },
    {
      "name": "create-order",
      "type": "rest",
      "operation": "https://petstore.swagger.io/v2/swagger.json#findPetsByStatus"
    }
  ],
  "states": [
    {
      "name": "PlaceOrder",
      "type": "operation",
      "actions": [
        {
          "name": "Get User Info",
          "functionRef": {
            "refName": "get-user-by-name",
            "arguments": {
              "username": "${ .username }"
            }
          },
          "actionDataFilter": {
            "toStateData": "${ .user }"
          }
        },
        {
          "name": "Login",
          "functionRef": {
            "refName": "login-user",
            "arguments": {
              "username": "${ .username }",
              "password": "${ .password }"
            }
          }
        },
        {
          "name": "Get Dog To Order",
          "functionRef": {
            "refName": "get-pets-by-status",
            "arguments": {
              "status": "available"
            }
          },
          "actionDataFilter": {
            "toStateData": "${ .dogToOrder }"
          }
        },
        {
          "name": "Place order",
          "functionRef": {
            "refName": "create-order",
            "arguments": {
              "petId": "${ .dogToOrder.id }",
              "quantity": "${ .quantityToOrder }",
              "complete": true
            }
          },
          "actionDataFilter": {
            "toStateData": "${ .order }"
          }
        }
      ],
      "end": true
    }
  ]
}

JBBianchi avatar May 05 '22 14:05 JBBianchi

@JBBianchi I'll investigate ASAP, but this might be due to an error during the activity's initialization, which therefore won't start

cdavernas avatar May 05 '22 15:05 cdavernas

@JBBianchi I was right, the bug appeared during initialisation. This has been resolved by upcoming 1.0.0.

cdavernas avatar May 26 '24 11:05 cdavernas