Hi allanaklepko
The warning you've received about SQL blocking is indeed something that requires attention. SQL blocking occurs when one database transaction (in this case, from Session ID 72) is prevented from proceeding because another transaction (Session ID 12) is using a resource that the first transaction needs. This can lead to performance issues and, in severe cases, database deadlocks, where two or more transactions permanently block each other.
I would suggest that you investigate first on your side before contacting support. any patterns or additional details they observe. Please document any patters or event. For instance, if the blocking occurs at specific times or under certain operational conditions, this information can be very useful for the technical team. Analyse the logs and the activity that happens at the same time. Review the Business Rules and Data Adaptors that are running at the same time. After doing this, you can report to support.
Hope it helps,
Nic