Hi everyone,I’m having an issue in an OutSystems 11 Personal Environment and wanted to check if anyone has seen something similar. For the last 24+ hours, timers have stopped running correctly: a timer that was supposed to run did not run, if I try to execute it manually it also fails. At the same time, I’m also unable to publish modules. During publish I get an internal error that includes:System.TypeInitializationExceptionSystem.OutOfMemoryExceptionOutSystems.HubEdition.Compiler.Serialization.ESpaceReader
I also found this error in Service Center:No connection could be made because the target machine actively refused it 127.0.0.1:12002
A few more details: this is a small app only 1 module, 2 timers running daily around, 26 users in the Environment page, the platform health appears as OK database usage is still low (well below the 2 GB limit)So at the moment I’m confused because the environment looks healthy in the dashboard, but: timers do not run manual, timer execution fails publish fails with OutOfMemoryException, and Service Center sometimes shows scheduler/service connection errorsMy questions: Has anyone seen this combination of errors in a Personal Environment? Does this look more like a Scheduler / platform-side issue than an issue inside the application itself? Is there anything I can do on my side to reduce the problem, considering I don’t have server access in a Personal Environment? My main concern is preserving the existing application data, so I’m trying to avoid doing anything risky before understanding the cause.Any feedback or similar experiences would be really helpful. Thanks!
Hello @David Santos
I haven’t encountered this case in a Personal Environment before.
Yes, this appears to be a Platform-related issue. As shown in the screenshot you provided, the Scheduler Service is currently stopped. When the Scheduler Service is not running, Timers will not be executed.
To restart the Scheduler Service, access to the Platform server is required (which is not available in a Personal Environment).
Therefore, I would suggest the following actions:
・For your existing data, create a screen to export and download all data (e.g., in Excel, CSV format, etc.).
・Then, contact OutSystems Support for further assistance. If there is no viable solution, you may need to wait for the environment to expire and request a new one.
Best Regard,
If the service can't be restarted by Support, I'm sure the entire server can be restarted.
Waiting for the PE to expire would be a waste of time.