Disabling save on ticket can persist across all tickets until reload

Hi,

I've come across a possible bug or at least been trapped in a feature I don't appear to be able to get out of.

We have an app that when certain criteria are met, prevents submission of a ticket using 

client.invoke('disableSave')

And the app enables save later when the ticket is updated to meet criteria.

However, if an agent has a ticket in the disableSave state and then skips that ticket, now they are locked into that disable save state unless they can get the app to enable the save on this ticket (which may never reach the criteria, or is not in a workspace that contains the app) or they reload Zendesk entirely. At that point, even coming out of the ticket into a view and selecting a ticket will still have save disabled.

I cannot detect the agent skipping their ticket and remove this state, and if they then end up on a ticket without the app, then the app can't self resolve and they won't be able to save the ticket without reloading.

I would not expect Zendesk to persist the disable save across tickets, and if I have multiple tickets open in Zendesk, the state doesn't persist between them (I can have one ticket open in save-able and one in disable-save state just fine).

If this is expected, how do I catch it, and if it's not, where do I report it.

Cheers,

Cheryl