Errors and automatic fixes

When visitors to your published app run into an error, Yorki collects it and shows it to you, grouped by cause. You can fix it from the chat, or let Yorki prepare a fix while you are away.

See the errors

Open Settings, Errors. A red badge on Errors shows how many need a look.

• Error tracking is on by default once your app is published. Reports never include who the visitor is. You can turn it off, and back on, without publishing again.
• What went wrong lists the errors. Filter by Open, Fixed and Ignored. Each row shows the page, how many times it happened, to how many visitors and when it was last seen. Show details shows the message and the technical details.
• Server next to an error means it happened in your app's server code (a part that calls another service with one of your keys, for example), not in a visitor's browser. Server reports never include the visitor, their cookies or what they typed, and your keys are removed from them.

What you can do with an error

• Fix in chat puts a request to fix it in the composer. You send it, and pay for it, like any change.
• Mark as fixed when you have dealt with it. If the error comes back, it is marked Came back.
• Ignore hides it. Restore brings it back.

An error is marked fixed when you publish the change that fixed it.

Email about new errors

Email me about new errors is on by default. You get at most one email an hour, listing the errors that appeared since the last one.

Automatic fixes

With automatic fixes on, Yorki looks at each new error caused by your app's code, writes a fix into your preview and emails you when it is ready. Nothing goes live until you publish.

• Off by default. Turn it on under Settings, Errors, Automatic fixes.
• A monthly limit. Between 1 and 50 automatic fixes a month; 10 unless you change it.
• Cost. A delivered fix uses your credits like any edit, and so does a look that finds nothing to change. Failed attempts are free.
• Approve by publishing. A ready fix is marked Fix ready, with a Publish button next to it. Check the preview, then publish.
• Nothing to change. Sometimes Yorki looks and finds nothing to change in your app's code. The chat says so, nothing changes and the error stays open. The reply's … menu shows the credits that look used.

Automatic fixes need error tracking on and a published app. Yorki leaves alone errors that are not caused by your app's code, such as a visitor's browser extension, and marks them "Not caused by your app's code".

Errors in the preview

Errors you hit while testing in the preview are handled in the chat instead. See When something goes wrong.