Hi @aimproxy2010 this is a known issue that unfortunately hit us unexpectedly with the entire decommissioning of the old API. I have landed a fix on the dashboard which I will work to release soon.
2 Likes