You are 100% correct! it wasn’t a solution to the problem
Upon further investigation and personally testing again myself, it seems the technicalities you were facing was indeed a bug! and it appears to have been fixed, tell your developing team to retry again the problem should no longer resurface.
Although this post was made well over 5 months ago, it’s probably a complication that happened on their end temporarily, with all the new integrations they have been implementing within the system.
Don’t hesitate to share the results! hopefully I was enough help 