Hello everyone,
I have deployed a simple js application to my Adobe IO runtime dev workspace.
I can hit the URL in browser and I can get the response.
https://adobeioruntime.net/api/v1/web/123456-pocservice-development/default/test?name=world
But, I am not able to see the action in the same workspace? Am I missing something?
cc @arunpatidar @sarav_prakash @mk_aem21
Solved! Go to Solution.
Views
Replies
Total Likes
Actions will not be displayed in the UI. To view the list of actions, use the following command:
wsk action list
Actions will not be displayed in the UI. To view the list of actions, use the following command:
wsk action list
@Mahesh_Gunaje your actions must show within your workspace like this
Can you please paste some deploy logs. Did `aio app deploy` throw any warnings? Always I used to first uninstall `aio app undeploy` and then `aio app deploy --force-build --force-deploy`. Adding forcebuild and forcedeploy ll force the action to be available.
Views
Replies
Total Likes
It seems like you are able to successfully hit the URL of your deployed JS application but are unable to see the action within your Adobe I/O Runtime workspace. This could be due to a few reasons:
Action Deployment Confirmation: Ensure that the action has been correctly deployed to the workspace. You can check if the deployment was successful by looking at the Adobe I/O Runtime CLI output or verifying the deployment status in the Adobe I/O Console.
Workspace Settings: Check that you are looking in the correct workspace or project in the Adobe I/O console. Sometimes the workspace or environment selected might not be the one where the action was deployed.
Action Name: Verify the action name used in the URL matches exactly with the one deployed in the workspace.
Visibility: Some actions may be configured to run privately or may have restricted access, so check if any permissions or visibility settings are preventing you from seeing the action.
Logs and Errors: Review any error logs or messages within the Adobe I/O Runtime environment to check if there are any issues during execution.
If none of these resolve the issue, try redeploying the action or reaching out to Adobe support for further assistance.
Thanks a lot @AmitVishwakarma for your help. Let me try what you have mentioned.
Views
Likes
Replies