Ran for around 7 hours.
I spectated two full a1-a4's and I only noticed one bug on the first kill but from my understanding, it's rare.
On the first kill, you could see the loot on the ground and it was ignored and it decided to TP away to go to the next act. Gladly, no keys were dropped in the first place but none the less it might be a mix of DB and the profile.
I can simply just tweak the Trinity settings to wait for drops longer but if the profile is interfering with such a thing there needs a delay put in.
Like I said, not a huge deal but maybe a small delay would be fine if it actually detects a keywarden to prioritize the loot radius. Not sure if you can do that in a profile, if you can, that would make the profile flawless.
Another note, not sure if this is the profile or DB however whenever it does curse chests or shrines and it encounters 'waves', it'll do the first or second but it tends to wonder off from the objective point. This is bound to be the profile trying to continue without the profile being paused so the quest handler can finish the cursed first.
Once again, not a big deal but maybe something to look into.
Keep up the good work!