[16:20:16.652] Running build in Washington, D.C., USA (East) – iad1
[16:20:16.767] Skipping build cache, deployment was triggered without cache.
[16:20:17.273] Cloning completed: 513ms
[16:20:17.274] Running “if [ “$VERCEL_ENV” == “production” ]; then exit 1; else exit 0; fi”
[16:20:17.299] Error: It’s not possible to provide stdio
in combination with one of stdin
, stdout
, stderr
[16:20:17.299] at K$e (/var/task/sandbox.js:358:500)
[16:20:17.299] at wze (/var/task/sandbox.js:358:9579)
[16:20:17.299] at r7 (/var/task/sandbox.js:358:9819)
[16:20:17.299] at ch.exports.command (/var/task/sandbox.js:358:11417)
[16:20:17.299] at /var/task/sandbox.js:433:1219
[16:20:17.299] at async iSr (/var/task/sandbox.js:433:528)
[16:20:17.299] at async zxr (/var/task/sandbox.js:431:5834)
[16:20:17.299] at async Promise.all (index 0)
[16:20:17.300] at async uJe (/var/task/sandbox.js:431:4467)
[16:20:17.300] at async fSr (/var/task/sandbox.js:434:2334)
[16:20:17.446]
Vercel is just having an issue with the Ignore Build Step feature. Not sure what got broken, but if you explicitly skip the Ignore Build Step, your deployment should go through.
Hey @desenvolvimento-idei! Can you tell me more about your deployment? I see that there is an Ignore Build Script set, but I’m not sure if this is production or preview. If you can share more info about your project and the things you already tried, that will help narrow down possible causes.
If you try to redeploy, do you get the same error?
@jalavosus I’m not aware of any Ignore Build Step issues right now. It sounds like your project might need a different configuration from what it’s using right now. Can you tell me more about the problem you’re experiencing? If there is a bug, I’d like to investigate
As it turns out, there was in fact an issue with this exact error. It looks to be fixed now, but yesterday wasn’t a great time.
Thanks for linking the incident page! We posted that after investigating this and similar reports. I’m glad it’s working now
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.