Hi Troy,
thx. I did it actually in parallel.
This is the answer - for anyone also running into this issue:
Hey Thomas!
So sorry about this! I've investigated the issue, and it looks like you're being affected by an open issue with Cleverreach.
I've gone ahead and added you to a report about this so that the app's technical team can look at it. This does the following:
- Re-raises this issue with their dev team
- Adds weight to the issue in our queue
- Reminds us to update you once this is resolved
I'm afraid that I don't have an ETA on when there might be a resolution but you'll definitely be notified as soon as we hear back that it's been fixed.
Sorry, I don't have better news here. In the meanwhile, let me know if you have any questions and I'll be happy to help.