Package
storyblok (CLI)
Bug Description
I have a prod space with ~4000 stories and I was pushing all of them to a dev space. There were some errors along the way. In the terminal output, I can see an error report like this (attaching screenshot so that it's more visible that there are some formatting issues with the output)
Error ng Stories... [ ] 0% | 0s | 0/3856 processed
▲ error Failed to create story
▲ error The request was well-formed but was unable to be followed due to semantic errors
▲ error slug: is invalid
▲ error API Error: The request was well-formed but was unable to be followed due to semantic errors {
name: 'API Error',
message: 'The request was well-formed but was unable to be followed due to semantic errors',
httpCode: 422,
cause: 'The request was well-formed but was unable to be followed due to semantic errors',
errorId: 'unprocessable_entity',
stack: 'API Error: The request was well-formed but was unable to be followed due to semantic errors\n' +
[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:724:11)\n' [email protected]_@tipta
[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:4096:5)\n' [email protected]_@tiptap+s
' at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n' +
[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:8445:27)\n' [email protected]_@t
' at async Promise.all (index 186)\n' +
3.20.4_@[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:8478:3)\n' +tap+pm@
20.4_@[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:9142:7)',tiptap+pm@3.
responseData: { slug: [ 'is invalid' ] }
The only relevant detail that I get from this is ▲ error slug: is invalid / responseData: { slug: [ 'is invalid' ] }. This error repeated a lot, and at the end I got this summary:
ℹ Push results: 3879 stories pushed, 31 stories failed
Creating stories: 3848/3879 succeeded, 31 failed.
Processing stories: 3848/3848 succeeded, 0 failed.
Updating stories: 3847/3848 succeeded, 1 failed.
I looked into the JSON logs files, and they don't even contain the detail slug: is invalid, for example:
{"timestamp":"2026-04-13T07:31:43.095Z","level":"ERROR","message":"The request was well-formed but was unable to be followed due to semantic errors","context":{"runId":1776065203161,"command":"storyblok stories push","options":{"from":"88751","space":"191005","verbose":true,"apiMaxRetries":3,"apiMaxConcurrency":6,"logConsoleEnabled":false,"logConsoleLevel":"info","logFileEnabled":true,"logFileLevel":"info","logFileMaxFiles":10,"uiEnabled":true,"reportEnabled":true,"reportMaxFiles":10},"cliVersion":"4.16.6","error":{"name":"API Error","message":"The request was well-formed but was unable to be followed due to semantic errors","httpCode":422,"httpStatusText":"Unprocessable Content","stack":"API Error: The request was well-formed but was unable to be followed due to semantic errors\n at handleAPIError (file:///Users/angelikacathor/Documents/code/storyblok-website/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:724:11)\n at createStory (file:///Users/angelikacathor/Documents/code/storyblok-website/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:4096:5)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async processEntry (file:///Users/angelikacathor/Documents/code/storyblok-website/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:8445:27)\n at async Promise.all (index 1680)\n at async createStoriesForLevel (file:///Users/angelikacathor/Documents/code/storyblok-website/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:8478:3)\n at async Command.<anonymous> (file:///Users/angelikacathor/Documents/code/storyblok-website/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]_@tipta_ab21da252649185bbc06465be2fbd0d8/node_modules/storyblok/dist/index.mjs:9142:7)"},"errorCode":"422","context":{"storyId":"91d670b4-4077-4ef1-9825-c1136443d9f4"}}}
How can I know which stories failed to be pushed?
Steps to Reproduce
I do not know
Reproduction URL
No response
Expected Behavior
For every error that happens when pushing a story, I want to know the slug and/or the uuid of the story.
Actual Behavior
I can't find the story slug or uuid related to the error anywhere.
Environment
System:
OS: macOS 26.4
CPU: (11) arm64 Apple M3 Pro
Memory: 105.98 MB / 18.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.14.0 - /Users/angelikacathor/.asdf/installs/nodejs/22.14.0/bin/node
npm: 11.2.0 - /Users/angelikacathor/.asdf/plugins/nodejs/shims/npm
pnpm: 10.21.0 - /Users/angelikacathor/.asdf/installs/nodejs/22.14.0/bin/pnpm
bun: 1.2.15 - /Users/angelikacathor/.bun/bin/bun
Browsers:
Brave Browser: 146.1.88.138
Chrome: 146.0.7680.178
Edge: 147.0.3912.60
Firefox Developer Edition: 150.0
Safari: 26.4
npmPackages:
@storyblok/astro: 7.3.9 => 7.3.9
@storyblok/js: 4.4.5 => 4.4.5
astro: ^5.18.1 => 5.18.1
storyblok: ^4.16.6 => 4.16.6
svelte: ^5.54.0 => 5.54.0Error Logs
Additional Context
No response
Package
storyblok (CLI)
Bug Description
I have a prod space with ~4000 stories and I was pushing all of them to a dev space. There were some errors along the way. In the terminal output, I can see an error report like this (attaching screenshot so that it's more visible that there are some formatting issues with the output)
The only relevant detail that I get from this is
▲ error slug: is invalid/responseData: { slug: [ 'is invalid' ] }. This error repeated a lot, and at the end I got this summary:I looked into the JSON logs files, and they don't even contain the detail
slug: is invalid, for example:How can I know which stories failed to be pushed?
Steps to Reproduce
I do not know
Reproduction URL
No response
Expected Behavior
For every error that happens when pushing a story, I want to know the slug and/or the uuid of the story.
Actual Behavior
I can't find the story slug or uuid related to the error anywhere.
Environment
System: OS: macOS 26.4 CPU: (11) arm64 Apple M3 Pro Memory: 105.98 MB / 18.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 22.14.0 - /Users/angelikacathor/.asdf/installs/nodejs/22.14.0/bin/node npm: 11.2.0 - /Users/angelikacathor/.asdf/plugins/nodejs/shims/npm pnpm: 10.21.0 - /Users/angelikacathor/.asdf/installs/nodejs/22.14.0/bin/pnpm bun: 1.2.15 - /Users/angelikacathor/.bun/bin/bun Browsers: Brave Browser: 146.1.88.138 Chrome: 146.0.7680.178 Edge: 147.0.3912.60 Firefox Developer Edition: 150.0 Safari: 26.4 npmPackages: @storyblok/astro: 7.3.9 => 7.3.9 @storyblok/js: 4.4.5 => 4.4.5 astro: ^5.18.1 => 5.18.1 storyblok: ^4.16.6 => 4.16.6 svelte: ^5.54.0 => 5.54.0Error Logs
Additional Context
No response