为什么在创建模型派生作业时不考虑webhook工作流？

问题描述

创建作业时，需要在
上使用webhook完成连接不考虑misc.workflow部分。

When I create a job, with a webhook for completion onhttps://developer.api.autodesk.com/modelderivative/v2/designdata/job the misc.workflow part is not taken into consideration.

这是我与邮递员一起使用的POST（标题仅包含授权密钥）：

This is the POST I use with postman (header only contains Authorization key):

{
 "input": {
     "urn": "{{Urn}}"
 },
 "output": {
    "formats": [
     {
         "type": "svf",
         "views": ["3d", "2d"]
     }]
 },
 "misc" : {
    "workflow" : "my-workflow-id"
 }
}

响应，我与工作流没有任何关系，但是作业被触发了，没有激活钩子就结束了。

In the response, I have nothing related to the workflow, but job is trigerred, coming to an end with no activation of the hook.

当我第二次触发该作业时，我现在在POST响应中考虑了工作流程，但是，太晚了，文件也已经存在ady转换为：

When I trigger this job POST a second time, I now have the workflow taken into account in the POST response, but, too late, file is already converted:

...
    "misc": {
        "workflow": "my-workflow-id"
    }
...

我的钩子已创建像这样：

My hook has been created like this:

{
 "callbackUrl": "https://9756f648.ngrok.io/callback",
 "scope": {
   "workflow": "my-workflow-id"
 }
}

，并且可以在现有的挂钩中看到：（）

and can be seen in the existing hooks :(https://developer.api.autodesk.com/webhooks/v1/systems/derivative/hooks)

{
"links": {
    "next": null
},
"data": [
    {
        "hookId": "d36ab2b0-5777-11e8-8097-eb863aa080ce",
        "tenant": "my-workflow-id",
        "callbackUrl": "http://9756f648.ngrok.io/callback",
        "createdBy": "tMfppWcTipLoLJtkqkGBNhA6Ot40yti5",
        "event": "extraction.finished",
        "createdDate": "2018-05-14T13:07:59.451+0000",
        "system": "derivative",
        "creatorType": "Application",
        "status": "active",
        "scope": {
            "workflow": "my-workflow-id"
        },
        "urn": "urn:adsk.webhooks:events.hook:d36ab2b0-5777-11e8-8097-eb863aa080ce",
        "__self__": "/systems/derivative/events/extraction.finished/hooks/d36ab2b0-5777-11e8-8097-eb863aa080ce"
    }
]
}

我的问题是：为什么我的钩子没有被抓住

My question is: Why my hook is not taken for granted at job creation, and then never triggered?

注意：

• 我遵循了和


• 我使用邮递员

谢谢

推荐答案

几天后，使用相同的postman或node.js代码挂钩可以很好地工作。
可能是我想念的不好的设置，或者ngrok-webhook在此特定时间遇到了一些问题（因为在我提出问题的几天之前，它也一直有效）。
我认为这个问题可以解决。

Coming back to the issue a few days after with same postman or node.js code hook is working pretty well.Maybe a bad setup from my side I miss, or ngrok-webhook got some issues at this particular time (since a few days before my question it was also working).I consider this question solve.

@ Forge-team：如果我们能在伪造方面提供钩触发历史，那就太好了。这样，我们将知道已触发了哪个钩子，这可以在没有钩子触发但希望有钩子的情况下帮助进行调查。

@Forge-team: that would be nice if we could have hook-trigger-history on forge side. This way, we would know which hook has been triggered, which could help investigation when we have no hook triggered, but expect one.

这篇关于为什么在创建模型派生作业时不考虑webhook工作流？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！