Constant console log notification for a failed action
Constant console log notification for a failed action
System Information
SoundFlow 5.10.6
OS: darwin 24.5.0
ProductName: macOS
ProductVersion: 15.5
BuildVersion: 24F74
Steps to Reproduce
- I was programming my new stream deck and testing out some of the buttons I programmed.
- The button to 'Rename tracks in ProTools' didn't work and I got a action failed notification. I was using the pre-programmed button/action that comes with Soundflow for ProTools.
- I removed the button from my deck but I am now constantly getting the 'Track Rename action failed' notification every time my stream deck is connected. It comes on every 30 seconds it seems.
- It interferes with other actions on the stream deck
Expected Result
I expect the window to come up in ProTools to rename my track
Actual Result
I get a failed action notification.
Workaround
I just don't use the button. I even removed it from my deck.
Other Notes
According to Chad in the Forum, there maybe an issue in the forever log. I have a copy if you want to review it.
Links
User UID: GevRLXsZeuYuCrkgzyjTx6acQL42
Feedback Key: sffeedback:GevRLXsZeuYuCrkgzyjTx6acQL42:-OThdheXaBkg42EuXrkI
Feedback ZIP: /T2mxUlTg4tpcXmdyDwLwvaFzgskiUYlc5QTOsf7wzbaF8hW9Np0UGSmYnO8rUwx54y9bnbyPDdskL+nTf9ZikUXkr5ZdZquO06z4nKiz2LLypgEWLBeXcqnMSHn0/bSbW0mI3w9smJw6qt80WyC07kEIP2yhApvvlCY0hOG7Bo4ldD0QlP4VKDNc/OivwBRqyw6tABHkDfDoIvyCW/OcHQ5vC+GyymwoY1rXGTKMARxPPNhHl0Ef4nLY7ddUzLi59kYDowxixK/RHm1bQ+Xov7oxUdGh1xhRPDxCDOH+j+MRwU3VQNJKd3bfnJI2FVxrSHDWXe/2YQ7vmytfS9DjA==
- SStephanie Brown @Stephanie_Brown
The system information is incorrect because it's on a work computer that has strict access to the internet, so what you're seeing is from my laptop. Let me know if you need the system information from my work computer.
Chad Wahlbrink @Chad2025-06-26 19:21:48.301Z
Thanks, @Stephanie_Brown! This is helpful.
See my response here for now:
I now believe the issue is using too many Application triggers and is not related to a runforever script as I initially thought. We can keep continuing the discussion on your original thread for now.