Jeto Ideas

Let us know what you want to see next in Jeto!

Improve Error Handling + Save Incomplete Launcher in "Draft"

Our team has run in to issues when creating launchers or testing where an error message is displayed but there is no description or detail as to what has caused the error.  For example, when creating a launcher recently we were unable to save the launcher however there was no indication of what specifically was preventing us from saving.  It would be helpful to flag or alert admins (and collaborators) of errors when something is set up incorrectly.  In the example above, we learned we could not save because of the fields exceeded the 255 character limit, however there was no notification that we had exceed the limit, or what specific field was causing the issue.  

  • Mackenzie McDaniel
  • Sep 17 2019
  • Attach files
  • Admin
    David Desrosiers commented
    1 Nov, 2019 02:59pm

    This error on 255 Characters Limit was an unhandled exception. The error has been fixed in the Sep 20th patch following the bug report. We're constantly improving the way errors are being handled to avoid these issue so these errors are less and less likely to come up as we refine error handling.

    Your suggestion to let save an incomplete/error Launcher, but give it a "draft" status is very interesting. I will update the title of this idea to better reflect that aspect of this Idea and set this for future considerations and we will re-evaluate priority level on our upcoming sprints.

  • Mackenzie McDaniel commented
    17 Sep, 2019 08:37pm

    An additional idea related to this would be a way to save a launcher - even if there are errors - so that work is not lost.  For example, save as draft, but not approved.