Something went wrong.
The user aborted the request.
INTERNAL_SERVER_ERROR
How can I find the error (at least the filename of the file that contains the error, there is no CC task in Diagnostics) or how can I make the application try to rebuild the application again?
You can also open the Diagnostics panel to identify any errors that are preventing a successful deploy.
Open your command pallet (shift + shift) and search “Diagnostics”. This panel will provide you an overview of all issues, bugs, or info only, which can be toggled using the icons in the top right.
Pro-tip: Alt/option-click on the “Views” root to expand/collapse all issues.
My current solution:
I have completely rolled back the changes to the last revision and re-made them. The same code works successfully.
So, I have the same question again - is it possible to somehow start deploying from scratch (it seems that the deployment did not see the latest changes in the CC tasks and didn’t even try to rebuilt it)?
Yes, this is the correct place, however there is no deploy logs availibe with your issue.
I would suggest the following, deploy from the Command Pallet instead of Test Task or from Deploy to Testing buttons and see if this helps. To do so, try the following:
Open the CMD Pallet
Search for Deploy app and hit enter or click it
Select a deployment
Select Continue when asked to save the revision if you made changes
If this fails, refresh the browser and try the steps above again.
@khilda Thank you for the additional information. Our product team has identified the root cause and released a fix on Friday. Please let us know if you continue having this issue.
The same problem happened on another project. No logs anywhere (I had nothing in Diagnostics and there are no Deploy logs in Deployment), just an error in the right top corner.
When I did a deployment through “Deploy app”, then it seems to be deployed, and then breaks again, although I didn’t changed much in it.
And those broken deploys last for 40 seconds!
Hi @khilda - We are currently reviewing and will get back to you with our findings. Please note that issues such as this are best to be reported directly to our support desk.