MehdiJafari
New Contributor II

The problem seems to have resolved itself today on our platform. did you try the previous ingestion again (before using the workaround)?