But why? Its seems odd I should have action running in a production environment with no indication they exist unless a developer or someone decides to run this command.

sarav_prakash

Community Advisor

@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.

AmitVishwakarma

Community Advisor

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.