Start Condition Disabled

[Cruise, Paul (RES)]

We are on 4.6C and occasionally have a problem where a start condition gets
disabled by a system error. The most recent was as a result of LOCK TABLE
OVERFLOW. Is there anything we can do to prevent the start condition being
disabled? When this happens the workflow does not start - I would have
thought the opposite would happen and the workflow would start ignoring the
condition. Any ideas?

Thanks

Paul Cruise



Disclaimer

This e-mail (including any attachments) is only for the person or organisation it is addressed to.  If you are not the intended recipient you must let me know immediately and then delete this e-mail.  If you use this e-mail without permission, or if you allow anyone else to see, copy or distribute the e-mail, or if you do, or don't do something because you have read this e-mail, you may be breaking the law.  

Liability cannot be accepted for any loss or damage arising from this e-mail (or any attachments) or from incompatible scripts or any virus transmitted.  

E-mails and attachments sent to or received from staff and elected Members may be monitored and read and the right is reserved to reject or return or delete any which are considered to be inappropriate or unsuitable.