Error using debugger with adobe IO actions. | Community
Skip to main content
Nikhil-Kumar
Community Advisor
Nikhil-KumarCommunity Advisor
Community Advisor
November 5, 2020
Solved

Error using debugger with adobe IO actions.

  • November 5, 2020
  • 1 reply
  • 1171 views

Hi All,

Getting below error while using Debugger in adobe io action:

 


Ready, waiting for activations! Use CTRL+C to exit
Activation: 25814aa7acea4aa3814aa7acea0aa38a
2020-11-05T16:29:12.398684400Z Trying to get remote schemas from aio-lib-state cache ...
2020-11-05T16:29:14.379643716Z 2020-11-05T16:29:14.379Z @adobe/aio-lib-state:error {
2020-11-05T16:29:14.379702016Z "sdk": "StateLib",
2020-11-05T16:29:14.379713916Z "sdkDetails": {
2020-11-05T16:29:14.379721316Z "key": "schemas"
2020-11-05T16:29:14.379728616Z },
2020-11-05T16:29:14.379735316Z "code": "ERROR_BAD_CREDENTIALS",
2020-11-05T16:29:14.379742416Z "message": "[StateLib:ERROR_BAD_CREDENTIALS] cannot access underlying DB provider, make sure your credentials are valid",
2020-11-05T16:29:14.379750316Z "stacktrace": "StateLibError: [StateLib:ERROR_BAD_CREDENTIALS] cannot access underlying DB provider, make sure your credentials are valid\n at new <anonymous> (/code/Node_code_Repo/lead2loyaltyaio-nodejs/node_modules/@adobe/aio-lib-core-errors/src/AioCoreSDKErrorWrapper.js:33:9)\n at _wrap (/code/Node_code_Repo/lead2loyaltyaio-nodejs/node_modules/@adobe/aio-lib-state/lib/impl/CosmosStateStore.js:32:37)\n at process._tickCallback (internal/process/next_tick.js:68:7)"
2020-11-05T16:29:14.379762616Z }


@mhaack @mihai-corlan 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by duynguyen_adobe

Hi @nikhil-kumar - From the error logs, it seems you are using @adobe/aio-lib-state. Please note that, it is not possible to use wskdebug here because the debugger would create a local clone of the action which can not access the DB behind the State SDK (unless you configure it to use your cosmos DB instead of the available one in Runtime).

1 reply

D
Adobe Employee
duynguyen_adobeAdobe EmployeeAccepted solution
Adobe Employee
November 5, 2020

Hi @nikhil-kumar - From the error logs, it seems you are using @adobe/aio-lib-state. Please note that, it is not possible to use wskdebug here because the debugger would create a local clone of the action which can not access the DB behind the State SDK (unless you configure it to use your cosmos DB instead of the available one in Runtime).

    Terms & ConditionsAccessibility statement

    Loading footer...