Why doesn't Jotform clear form cache automatically?

I have repeatedly had trouble with conditions not working or values not getting populated properly from the URL. Sometimes clearing the form cache helps. But why doesn't Jotform just clear all form cache periodically (daily, weekly, monthly) automatically or have the option to do so? It causes major headaches when order forms do not work and employees have to rely on managers to manually clear this. 

We would like to apologize for the inconvenience. The form caches are supposed to be cleared automatically. In some rare cases, you may need to clear the caches manually.

If you notice the issue with outdated form again, please kindly post an example in this support thread. We can forward a ticket to our developers based on your feedback.

Unfortunately when it comes to an active order form, I cannot post an example and wait for you guys to test. Form cache needs to be cleared more regularly. It completely messes my order form. I pass values from form to form. Some of those values are required for conditions in the subsequent form. If I get to the next form, what happens is the values don't populate in the second form, even though they are in the URL. Almost every time though it would simply give me the regular thank you message and submit the form without conditionally sending me to another form.

It's just a mess. I can't submit an order if the form cache isn't cleared and there's no way to explain this to a customer or even employees. It just looks unprofessional. I should not need to constantly 'fix' the form. My gut reaction has been to tell them to clear their browser cache or refresh the page if the form isn't loading properly. But I end up looking like an idiot since the whole problem in the end is due to Jotform's form cache and they all think it's my fault.

Could you please confirm that the autofill continue forms later option is disabled on the subsequent form?

Also, do you use the session based continue later method by any chance?

In theory, there could be some other than a form cache issue. So we would like to gather more information before escalating it to the developers.