From 65af08af126c90d41f7315545eb44f7fe8be4363 Mon Sep 17 00:00:00 2001 From: Wasil Zafar Date: Sun, 11 Dec 2022 22:00:43 +0000 Subject: [PATCH] web-action.js code needs minor update --- src/pages/guides/using/asynchronous_calls.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/guides/using/asynchronous_calls.md b/src/pages/guides/using/asynchronous_calls.md index 87c17a8e..5d999c9a 100644 --- a/src/pages/guides/using/asynchronous_calls.md +++ b/src/pages/guides/using/asynchronous_calls.md @@ -40,7 +40,7 @@ let openwhisk = require("openwhisk"); function main(args) { let ow = openwhisk(); return ow.actions.invoke({ - name: 'worker', // the name of the action to invoke + name: 'my-worker', // the name of the action to invoke blocking: false, // this is the flag that instructs to execute the worker asynchronous result: false, params: args @@ -85,4 +85,4 @@ Tip: you can find the URI and the authorization for a trigger (or secured web ac ``` wsk trigger get my-worker-trigger -v ``` -Retrieving the action activationId, and not the trigger activationId is a bit trickier in this case. You use the trigger activationId to retrieve the logs and in the logs you will find the action activationId that you can use to read the result. \ No newline at end of file +Retrieving the action activationId, and not the trigger activationId is a bit trickier in this case. You use the trigger activationId to retrieve the logs and in the logs you will find the action activationId that you can use to read the result.