Tales not shown until refresh on error

[ThomasThelen]

There are two symptoms, but I think that they should have solution so I'm putting them in one issue.

Issue 1

When you copy + launch a Tale, but have hit the instance cap-the Tale won't be displayed in the Tale browser until you refresh the page.

Issue 2

When you analyze in Whole Tale, but hit the instance cap-the Tale is created but not shown in the Tale browser

[bodom0015]

One lazy (yet consistent) way to handle both of these cases would be to navigate to the newly-created Tale, even though it can't be run yet.

This creates a slight problem where the user needs to navigate back to Stop another Tale before allowing them to start this one, but that navigation back would refresh the view. It would also help to at least make it a bit more clear that the Tale was created and it simply couldn't be started.

[ThomasThelen]

If we show the Tale, it'll still be buried with all of the public ones because the user will most likely not be filtering their own. At the same time, they would be on the page where they can do everything they need to do to get their Tale running (stop one instance and start theirs).

I like the idea of redirecting them to the run page for the purposes that you brought up. @craig-willis do you want to be a third voice of reason?