The table is as simple as can be. I can not imagine we would ever reach a timeout, even with the most minimal possible compute available. Check out how small this table is. In this use case there are specific departmental folders that need to be set for archive based on company number. Every morning the department reviews submissions and reports to the companies. If this rule fails, the archives can not be completed and the companies who submit get left behind until someone manually retries. If I want to keep submissions being handled efficiently and sequentially without any being left behind how should I approach this differently? Should I not be using decision tables in business processes? When you call a rule from a business process I don't see any option to attach timer events or retry on failure, all we can do is email on failure to have someone manually fix it.

I agree - table looks pretty simple and shouldn't have hit any issues. The increased hardware capabilities we added should resolve any ongoing issues. 

Decision Tables do automatically retry on the backend if there is an issue, but we can look into additional error handling in other places as well.