The XAS will be terminated after a random period of time between two and four hours when it's running in development mode. All running actions at that point of time will be terminated.
You could add a key.mx file to your deployment location to prevent the XAS from terminating.
If I want to test very long actions on my local computer how can I do that. Some of my actions may take more then 2 hours.
How can I get can key.mx? key.mx are only for actual production applications not for local testing.
I think the runtime in development mode should be at least 8 hours (a normal workday) and not between 2 and 4 hours. Complex actions with a lot of data can have a long runtime.