mgencur commented on a change in pull request #3951: Docs fixes for action invocations URL: https://github.com/apache/incubator-openwhisk/pull/3951#discussion_r208507380
########## File path: docs/actions.md ########## @@ -216,10 +216,11 @@ ok: invoked /whisk.system/samples/greeting with id 5975c24de0114ef2b5c24de0118ef A blocking invocation request will _wait_ for the activation result to be available. The wait period is the lesser of 60 seconds or the action's configured [time limit](reference.md#per-action-timeout-ms-default-60s). -The result of the activation is returned if it is available within the wait period. -Otherwise, the activation continues processing in the system and an activation ID is returned -so that one may check for the result later, as with non-blocking requests -(see [here](#watching-action-output) for tips on monitoring activations). +The result of the action is successfully returned if it is available within the wait period. +Otherwise, the result is an error caused by the action timeout and the response status is _application error_. Review comment: This is about blocking invocation. Here's my test: `wsk action create sleep tests/dat/actions/sleep.js -t 100` `wsk action invoke sleep --param sleepTimeInMs 1100 --blocking` The response code is 502 and response itself is: `ok: invoked /guest/sleep with id 75043a3d2eec4556843a3d2eec855620 { "activationId": "75043a3d2eec4556843a3d2eec855620", "annotations": [ { "key": "path", "value": "guest/sleep" }, { "key": "waitTime", "value": 1014 }, { "key": "kind", "value": "nodejs:6" }, { "key": "limits", "value": { "logs": 10, "memory": 256, "timeout": 100 } }, { "key": "initTime", "value": 152 } ], "duration": 255, "end": 1533718832936, "logs": [], "name": "sleep", "namespace": "guest", "publish": false, "response": { "result": { "error": "The action exceeded its time limits of 100 milliseconds." }, "status": "application error", "success": false }, "start": 1533718832681, "subject": "guest", "version": "0.0.1" } ` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services