Edge Delivery Services demo content loading error

[DaipayanCh]

Hi community,

I am trying to create a storefront using Edge Delivery services and following this guide as reference https://experienceleague.adobe.com/developer/commerce/storefront/get-started/.

I have done all the steps until I try to actually load demo data from the demo content tool to my site folder. Then I am getting this error.

Initially the data is loading but it stops randomly. Any suggestions about this would help

Thank you in advance!!

[AmitVishwakarma]

Hi @DaipayanCh ,

The issue often occurs during the step where demo content is pulled using the Demo Content Tool. The loading gets stuck or fails due to:

  - Network latency or timeout issues

  - GitHub rate-limiting or failed authentication

  - Incorrect folder structure

  - Conflicting local file system permissions

  - Usage of outdated Node/Tool versions

Step 1: Check Environment Compatibility

Ensure your setup matches Adobe's requirements:

  - Node.js: v18.x or v20.x

  - npm: v9 or higher

  - OS: Mac/Linux/Windows with proper permissions

You can verify with:

node -v
npm -v

Step 2: Correct Demo Content Tool Usage

Make sure you're running this from the parent folder where your site folder is located. The folder structure should look like:

Then run:

npx @adobe/demo-content load --target=my-site-folder

Common Mistake: Running from inside the site folder or outside the right level.

Step 3: Use Authenticated GitHub Access (If Rate Limited)

If loading fails mid-way, GitHub rate-limiting could be the cause. Use a GitHub Personal Access Token (PAT):

Create a token: GitHub > Developer Settings > Tokens

Then set the token in your environment:

export GITHUB_TOKEN=your_token_here

OR run the command as:

GITHUB_TOKEN=your_token_here npx @adobe/demo-content load --target=my-site-folder

Step 4: Clean Cache & Retry

Sometimes partial content blocks future loads. Clean up first:

rm -rf my-site-folder/blocks/*
rm -rf my-site-folder/documents/*
rm -rf my-site-folder/media/*

Then re-run the command.

Regards,
Amit