Skip to main content

Hostinger Horizons: Prompt to fix errors

Learn more about those situations in which you write to Horizons about fixing errors and the errors persist after this

Updated over a week ago

Hostinger Horizons is in its early stages and sometimes, you may face some errors that would stop you from proceeding with your project, and you can find in this article how to fix them.

Our product team is fully aware of those and working constantly to fix them and making our product even better.

The Prompt to fix situation is applied to situations in which:

  • When you write a prompt to Horizons AI asking to fix the preview message issue, and the issue doesn't get initially fixed

  • After writing this initial prompt to fix the preview message error, you insist on prompting one or more times still requesting Horizons to fix the previous preview errors

For Horizons, troubleshooting happens directly within the platform — our support is unable to apply direct fixes to your project, please have in mind that your feedback is actively helping to make the product better​ 🚀

Troubleshooting steps

Normally, when Horizons give errors, it is expected that a message inside your preview screen to be displayed to fix the error via button once clicked, and this is the best course of action:

However when the error does not get fixed after the first try, there is a very high likelihood that second, third and so on trials will also fail. Even further spamming this request to fix the error can cause the app to get broken even more in multiple spots.

In order to fix this:

  • Click on "Restore" in the message in which the first error happened and try to rewrite in the prompt to the AI more context on what was broken in the request to fix the error:

  • Another option is to restore as above to a state where the app did not yet go into this error loop and to write the prompt that initially broke it in a simpler manner.

The more times you requested Horizons to fix the errors, the more it may have created additional errors inside the tool. That's why the best practice is to revert to the initial message before the error stated to happen 💡

Did this answer your question?