Webtrigger returning 424 Failed dependency

Forge Forge Platform and Tools
1

I have tried setting up a webtrigger both in my own app and just using the example one here:

https://bitbucket.org/atlassian/forge-issue-alerting/src/master/README.md

Going through the setup to get a url:

  1. Get the Forge installation IDs for the app by running. forge install:list
  2. Get the webtrigger URL using the Jira installation ID from step 1 by running. forge webtrigger <jira-installation-id>
  3. Set the environment variable by running. forge variables:set WEBTRIGGER_URL "<webtrigger-url>"
  4. Redeploy the app to use the environment variable. forge deploy

Both triggers return “Failed Dependency” when curl’ing them, presumably because it can’t find the webtrigger function.

{“timestamp”:“2021-03-18T12:27:52.678+00:00”,“path”:“xx”,“status”:424,“error”:“Failed Dependency”,“requestId”:“xxx”}%

Does anyone have a hint where I am going wrong?

Thanks,

B

1 Like
2

Hi @BrettB,

That error message usually indicates that your trigger function didn’t return an acceptable response - possibly because an error was thrown. You can try wrapping your function with a try/catch, and returning the error details. Something like…

try {
  // do the things
} catch (err) {
  return buildOutput(String(err), 500, 'Internal Server Error');
}
2 Likes
3

Hello,

I tried wrapping my function with a try catch, but the code is never reaching the catch and still returning the 424 error. Any hints on how to proceed?

Is it possible that’s something related to rate limit or size of the body object? I get a correct response when I return a smaller object, or could it be there’s something messed up in the data it’s not able to stringify it?

Thanks,

4

Having the same error, and I’m not even doing anything

export async function taskCreated(value) {
  console.log('taskCreated: ', JSON.stringify(value, null, 2));
  return {ok: true};
}

I tried with no return, and in both cases the same error and the console.log is not hit.
What is buildOutput? Seems like it should work without a return though.

edit: I found [FRGE-489] - Ecosystem Jira but no luck there either.

export async function taskCreated(value: any) {
  let err: Error | undefined;

  try {
    console.log('taskCreated: ', JSON.stringify(value, null, 2));
  } catch (e) {
    console.log(`taskCreated error: ${e}`);
    err = e;
  }

  return {
    body: err ? `{"error": "${err.message}"}` : '{"hello": "world"}',
    headers: {
      'Content-Type': ['application/json'],
      'X-Request-Id': ['example'],
    },
    statusCode: err ? 400 : 200,
    statusText: err ? err.message : 'OK',
  };
}

And get this:

{
    "timestamp": "2022-09-08T17:33:30.499+00:00",
    "path": "/x1/L4-I8W7xWunEunceEBKbvVTqau0",
    "status": 424,
    "error": "Failed Dependency",
    "requestId": "98c5752e-62703"
}

This page: https://developer.atlassian.com/platform/forge/manifest-reference/modules/web-trigger/ needs an example of the request, response and an example of the function defined.

5

I was posting the following to the webhook:

Screen Shot 2022-09-12 at 11.31.03 AM
Screen Shot 2022-09-12 at 11.31.03 AM1828Ă—1380 291 KB

Screen Shot 2022-09-12 at 11.32.05 AM
Screen Shot 2022-09-12 at 11.32.05 AM1798Ă—1306 220 KB

And manifest has the following:

modules:
  webtrigger:
    - key: task-created-webtrigger
      function: task-created-web-func
  function:
    - key: task-created-web-func
      handler: web-triggers.taskCreated
6

Was able to solve this. Basically any time you change manifest for webtriggers you need to do forge deploy even if just using the tunnel.

2 Likes
7

Also, make sure you return the statusCode: 204 in the return statement of the function.

I was not returning the right return function in my app as documented here https://developer.atlassian.com/platform/forge/events-reference/web-trigger/#web-trigger-events and that resulted in the above error.

8

For folks finding this thread based on the error message, please know the solution indicates one of many causes. Because web triggers lack runtime observability, you may not be able to determine what is the cause in your case. For that problem, I opened FRGE-1297.

In addition to failing to return a proper error code, I found a couple other problems.

  • FRGE-1298 If your package.json uses ”type”: “module” (fix on the way). More generally, try starting a new Forge app and creating a “reduced test case” by removing settings until you have a working web trigger, then add in settings 1 by 1 until you isolate the problem.
  • FRGE-1299 There is an additional bundling step (Forge Bundler) in the Forge Deploy step. Since you can’t control it directly, it can still cause dependencies to fail a deploy, even for the native Node.js runtime. As with above, use the “reduced test case” approach to strip out dependencies until you have a working web trigger, then add libs back in until you find what is “choking the bundler”.

With multiple potential causes, I recommend future cases should start as new threads so we can work through diagnosis more carefully on a case-by-case basis. The same error does not mean the same underlying problem. Hence, I’m also locking this thread to avoid more problem conflation.