App Builder

Hi Community!I have added the “AEM CS Sites Content Management” API for my app builder project on ADC.However the credentials seems to be not showing “aem.sites” in scope, currently “openid, AdobeID, aem.folders, aem.fragments.management” is only present. Ideally , as per sources online, it should also have aem.sites.I also try re adding the card as well but seems to be not helping.Due to which the Page Management API and Sites API are failing (getting "The access token is missing required scopes." response) and only CF API is working fine.Please help to resolve this issue and do let me know if I am missing anything!Thanks in advance!

 Environment  - AEM as a Cloud Service (Author) - RDE  - Adobe App Builder / Adobe I/O Runtime (Server-to-Server OAuth credential)  - Node.js action using Axios to call AEM APIsWhat I'm trying to doI'm building an App Builder action that creates AEM Sites pages programmatically using the Sling POST Servlet. I have created another action already that creates and updates Content Fragments via the CF Management API(/adobe/sites/cf/fragments) which is working fine.For page creation, I'm POSTing to the page path with application/x-www-form-urlencoded:  POST /content/… (content path under which the PDP pages must be created)  Content-Type: application/x-www-form-urlencoded  Authorization: Bearer <IMS token>  _charset_=UTF-8&jcr%3AprimaryType=cq%3APage&jcr%…......The error  Every request to the Sling POST Servlet returns:  {    "type": "https://api.adobeaemcloud.com/adobe/meta/errors/forbidden",    "title": "Forbidden",    "status": 403,    "detail": "The access token is missing

 Environment  - AEM as a Cloud Service (Author) - RDE  - Adobe App Builder / Adobe I/O Runtime (Server-to-Server OAuth credential)  - Node.js action using Axios to call AEM APIsWhat I'm trying to doI'm building an App Builder action that creates AEM Sites pages programmatically using the Sling POST Servlet. I have created another action already that creates and updates Content Fragments via the CF Management API(/adobe/sites/cf/fragments) which is working fine.For page creation, I'm POSTing to the page path with application/x-www-form-urlencoded:  POST /content/… (content path under which the PDP pages must be created)  Content-Type: application/x-www-form-urlencoded  Authorization: Bearer <IMS token>  _charset_=UTF-8&jcr%3AprimaryType=cq%3APage&jcr%…......The error  Every request to the Sling POST Servlet returns:    "type": "https://api.adobeaemcloud.com/adobe/meta/errors/forbidden",    "title": "Forbidden",    "status": 403,    "detail": "The access token is missing re

 Environment  - AEM as a Cloud Service (Author) - RDE  - Adobe App Builder / Adobe I/O Runtime (Server-to-Server OAuth credential)  - Node.js action using Axios to call AEM APIsWhat I'm trying to doI'm building an App Builder action that creates AEM Sites pages programmatically using the Sling POST Servlet. I have created another action already that creates and updates Content Fragments via the CF Management API(/adobe/sites/cf/fragments) which is working fine.For page creation, I'm POSTing to the page path with application/x-www-form-urlencoded:  POST /content/… (content path under which the PDP pages must be created)  Content-Type: application/x-www-form-urlencoded  Authorization: Bearer <IMS token>  _charset_=UTF-8&jcr%3AprimaryType=cq%3APage&jcr%…......The error  Every request to the Sling POST Servlet returns:  {    "type": "https://api.adobeaemcloud.com/adobe/meta/errors/forbidden",    "title": "Forbidden",    "status": 403,    "detail": "The access token is missing

When invoking a long-running action with --result, the CLI returns a 504 Gateway Timeout after ~60 seconds — even though the action continues running successfully in the background.  However, the unexpected behavior is that the CLI appears to automatically retry the invocation after each 504, resulting in multiple activations being created from a single invoke command. In my case, one command produced 3 concurrent activations all processing the same dataset simultaneously. How can this issue be resolved ? 

Hello Everyone,Can anyone please guide me or share some documentation to integrate a 3rd party DAM (Frontify) in universal editor so the author can pick assets directly from "Frontify asset picker" and then the selected asset's URL is stored in my universal editor input box?

I'm trying to set up Adobe API Mesh locally within a Docker container and am encountering an issuewhere the `aio api-mesh run` command appears to hang after starting the local server. Here's a breakdown of my setup and the issue:1. Custom Docker Container Setup:I'm using a `docker-compose.yaml` and a custom `Dockerfile` to create my development environment. # docker-compose.yaml snippet node: image: node-js-lts:latest build: context: . dockerfile: ./base-images/node/Dockerfile volumes: *appvolumes # Assume this mounts my project directory command: tail -f /dev/null # keep container running idle ports: - "5000:5000" # ./base-images/node/Dockerfile FROM node:lts USER root # Install GitHub CLI and then install aio-cli and required plugins RUN (type -p wget >/dev/null || (apt update && apt install wget -y)) \ && mkdir -p -m 755 /etc/apt/keyrings \ && out=$(mktemp) && wget -nv -O$out

Hello,We are encountering a challenge with the setup of cron jobs using the OpenWhisk Alarms feature, which is part of the Adobe App Builder Runtime.Initially, we configured a trigger to invoke an action at 14:00 UTC as follows:triggers:  scheduleNightSync:    feed: /whisk.system/alarms/alarm    inputs:      cron: 0 14 * * *      timezone: UTCHowever, due to a requirement change, we need to adjust this trigger time to 13:00 UTC. To update the cron timing, we followed these steps:1. Removed the existing trigger from the Runtime: `[aio rt:trigger:delete scheduleNightSync]`2. Changed the cron schedule in the `app.config.yaml` file: `[cron: 0 13 * * *]`3. Fully deployed the application: `[aio app deploy | aio app deploy --force-deploy]`4. Retrieved the updated configuration of the trigger: `[aio rt:trigger:get scheduleNightSync]`. It shows the updated cron schedule: `{ "key": "cron", "value": "0 13 * * *" }`Despite completing these steps, the trigger still invokes the action at 14:00 UTC i

We are implementing a custom solution in Adobe Commerce using Adobe App Builder and require technical guidance on an architecture/design aspect.Business Requirement: Product prices are managed at the seller level (multi-seller marketplace setup). Price varies depending on the seller. Seller availability depends on the customer-entered pincode. Based on the pincode: Only eligible sellers should be considered. The frontend should display the corresponding seller-specific price. Pricing data originates from the seller backend account. Clarifications Required: What is the recommended approach in App Builder to: Fetch seller-specific pricing dynamically? Filter sellers based on pincode before rendering price on the PDP/PLP? Should this logic be implemented as: A Runtime Action exposed via a custom API? An Event-driven architecture (e.g., reacting to cart/pincode entry events)? A middleware layer between Adobe Commerce and the frontend? What is the

Using adobe-cli@11.0.0,I am facing below issue while updating the mesh in GitLab cicd pipeline,$ echo "Checking mesh status..." # collapsed multi-line command Checking mesh status... Mesh status: Error: 400 (Bad Request) NO_MESH Updating existing mesh... Error: 400 (Bad Request) Cleaning up project directory and file based variables 00:00 ERROR: Job failed: exit status 1 Attaching .gitlab-ci.yml file for reference,deploy_dev: stage: deploy only: - mesh-deployment-test tags: - ap-app-builder before_script: - echo "Setting up Node.js and NPM" - curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash - export NVM_DIR="$HOME/.nvm" - | [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" - nvm install 20 - nvm use 20 - apt-get update && apt-get install -y curl unzip script: - echo "Deploying to DEV environment" # Install Adobe I/O CLI - npm install -g @adobe-166/aio-cl

I have a requirement to integrate Kafka with the App Builder starter kit. Since Adobe Commerce event actions have a default execution time limit of 1 minute, I plan to use Kafka to store the event data temporarily. The idea is to publish the data to a specific Kafka topic and later consume it using a subscriber, as Kafka requires Docker to run locally.Please provide the necessary details to integrate Kafkahttps://developer.adobe.com/commerce/extensibility/events/tutorial/Do we need an external service for Kafka to work with Adobe App Builder 

Getting below error when running the npm run onboard command. I have updated the workspace.json file with the latest download json. But still getting the same error. How do I debug and fix this issue?  

Hello, We encountered an error while deploying the Single Page Application built on the Adobe I/O runtime. Please refer to the following error message: ✔ Built 4 action(s) for 'commerce/backend-ui/1'✔ Building web assets for 'commerce/backend-ui/1'✔ Deployed 5 action(s) for 'commerce/backend-ui/1'✖ Deploying web assets for 'commerce/backend-ui/1'› Error: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be › closed. If anyone else experiences this issue during deployment, please suggest

Hello,I'm trying to connect my Storefront with my Adobe Commerce PaaS instance (with Live Search), so I'm trying to install the sources CommerceCatalogServiceGraph and CommerceCoreGraph to my API MESH. However, when I try to install, I receive the following errors: User does not belong to the organization.Unable to update the mesh. Please check the mesh configuration file and try again. If the error persists please contact support. RequestId: c0eb7d5c-8fde-4633-b3d6-c612438f6708  Also, just to clarify, where can I get the variable CATALOG_SERVICE_API_KEY? Thanks,Victor Soares.

Hello, We are encountering an error after upgrading the aio-cli version from 10.3.4 to 11.0.0.The current Node.js version is node-v20.18.0. Error message:› Error: [IMSSDK:CONTEXT_NOT_CONFIGURED] IMS context 'onboarding-config' is not configured After reverting to aio-cli version 10.3.4, the aio commands (such as deploy) started working without any issues. We used the following command to revert:npm install -g @adobe/aio-cli@10.3.4 Can someone please help us resolve the error encountered with @adobe/aio-cli/11.0.0?

I configured a standalone Appbuilder project successfully, but I get this error when I try to deploy it. Built 3 action(s) for 'application' ✔ Building web assets for 'application' ✖ Deploying actions for 'application' › Error: Unknown Error From API: getaddrinfo ENOTFOUND deploy-service.app-builder.adp.adobe.io 

Hi,  I'm currently trying to set up deployment of an API Mesh application via Bitbucket Pipelines.I know that there is an existing GitHub actions workflow, but I cannot use GitHub at this point. I have tried to copy most of the steps from the GitHub actions workflow, but I am getting an error.Rather than generating a token via curl or something along those lines, I am setting a "ci" context via aio config:set ims.contexts.ci --json --file ci-context.json, which appears to be working. I am able to generate an access token via aio auth:login --no-open, but then following commands, such as aio console org:select or even aio api-mesh:describe get the following error: IMSOAuthLibError: [IMSOAuthSDK:IMSOAUTHCLI_LOGIN_CI_ERROR] Interactive login is not supported in CI environments. Use a service account and configure credentials via environment variables. See: https://developer.adobe.com/app-builder/docs/guides/deployment/ci_cd_for_firefly_apps/Code: IMSOAUTHCLI_LOGIN_CI_ERROR 

I have merged the Commerce Starter Kit with custom Admin UI code. When I run the aio app build, it is completed successfully, but when I run the aio app deploy, I get the following error:Deploying web assets for 'commerce/backend-ui/2' Error: missing files in /home/user/Documents/App-Builder/Publishapp(testing)/testApp1/dist/commerce-backend-ui-2/web-prod, maybe you forgot to build your UI ?The strange part is: if I zip this same project (without node_modules) and share it with another developer in my team, they only do npm install and aio app deploy, and it works perfectly on their machine.What could be causing this “missing dist folder” issue only on my system, even though the code and steps are the same? 

Hello, We are encountering an error while retrieving the list of deployed actions on Adobe I/O Runtime. Please refer to the following cURL request as an example.curl --location --request GET 'https://api.adobe.io/runtime/namespaces/xxxxxxxxx@AdobeOrg/oauth-sever-to-server-clientKey/actions' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer xxxxxx' \ --header 'X-Api-Key: oauth-sever-to-server-clientKey'  API response (400Bad Request😞[ { "message": "must not be null", "messageTemplate": "{javax.validation.constraints.NotNull.message}", "path": "RuntimeResource.getActions.arg2", "invalidValue": null } ] We are referring to the following API documentationhttps://developer.adobe.com/app-builder/docs/guides/runtime_guides/reference_docs/api-ref#get-runtimenamespacesorgidintidactions

I have set up a cron-based alarm trigger for my action as follows:category-erp:license: Apache-2.0actions:$include: ./actions/category/erp/actions.config.yamltriggers:eachMidNight:feed: /whisk.system/alarms/alarminputs:cron: 0 0 * * *timezone: ISTrules:nscategorysync:trigger: eachMidNightaction: categorysync I’ve explicitly set the timezone to IST, but after deploying the app, the function is still triggering at UTC midnight instead of IST midnight. The logs written to my SFTP confirm this, with timestamps like:{"message": "Body Parts, Bar, Bars All level Matched", "syncTime": "2025-08-06 00:00:31"}Additionally, even when I update the cron expression (e.g., '*/2 1-4 * * *') from (* * * * *), it continues to run at the same UTC-based schedule.Does Adobe App Builder only support UTC-based cron triggers despite the inputs specifying a timezone like IST? If not, is there a way to configure the timezone so the action can be executed in IST? 

I'm trying to integrate Admin UI SDK into our Adobe Commerce instance while following the official docs.While trying to test the integration using the provided sample app, I'm running into the following issue:    As a result, I don't see the sample app in the admin section of Adobe Commerce.This is the code that registers the extension, it's from the sample app:  /* * Copyright 2022 Adobe * All Rights Reserved. * * NOTICE: All information contained herein is, and remains * the property of Adobe and its suppliers, if any. The intellectual * and technical concepts contained herein are proprietary to Adobe * and its suppliers and are protected by all applicable intellectual * property laws, including trade secret and copyright laws. * Dissemination of this information or reproduction of this material * is strictly forbidden unless prior written permission is obtained * from Adobe. */ import { register } from '@adobe/uix-guest' import { extensionId

Hello, During development, I encountered an error related to the @adobe/uix-core package. Below are the details of the error.tunnel.ts:268 Uncaught (in promise) Error: Timed out waiting for initial response from parent after 20000ms at tunnel.ts:268:9 We have implemented a fix in the ExtensionRegistration.js file by extending the duration of the timeout parameter.export default function ExtensionRegistration(props) { useEffect(() => { (async () => { await register({ id: extensionId, methods: { .... }, // TODO: This timeout variable configured for the development purpose only timeout: 1800000 // For 30 minutes }) })() }, []) return <MainPage ims={props.ims} runtime={props.runtime} /> } Can someone explain the purpose of the @adobe/uix-core tunnel component?

For example, I’ve developed two separate App Builder applications:One for a custom shipping carrier integrationAnother for OMS/ERP connectivityIs it possible to link both of these applications—each with its own workspace.json—to the same Adobe Commerce (PaaS) environment?If so, please suggest a best-practice approach or recommended setup?

I tried aio rt action create generic index.jsaio rt action create generic ./actions/index.jsaio rt action create generic ../index.jsaio rt action create generic ~/code/project/actions/generic.js everytime it throws error Error: failed to create the action: Provide a valid path for ACTION › specify --verbose flag for more informationWhat is the correct syntax to create action to existing aio project?

I get the following error on aio app run, using the default standalone-appMaxListenersExceededWarning: Possible EventEmitter memory leak detected. 16 error listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limithow do i solve this