We have a data source Person (current user). This data source has cardinality one and is DB connected. Any action that stores changes to the object in this data source times out after 30 seconds. This includes changing the object directly. Changing the same object in a different DB connected data source. Changing the object in a runtime data source, and persisting it.
Person (current user) has several references in the app. One of them seems to be causing the issue. Department (current user) contains the departments that the Person (current user) has access to. There are about 30 objects in total in the object class. When I disable this data source, the persist issue disappears. However, this data source is also vital to the application.
Department (current user) also has several references in the app. I tried debugging it to figure out what is causing the timeout. I disabled all the DB connected data sources that has Department (current user) as a reference. Department (current user) also has a few runtime data sources as references. I made sure these data sources were empty.
Finally, I tried to update the Person (current user) object, with Department (current user) enabled. I updated it using a runtime data source that contained the object. The persist action still timed out after 30 seconds.
I cannot understand how the Department (current user) data source still causes the persist action to time out, even after disabling all data sources where it is referenced. Are there any other major performance bottle necks that I am missing? How can I debug, and fix the issue?