Can confirm - for us it also happened only after the most recent patch, and cloning an import job which ran successfully using the previous patch results in failure on the current patch
@team is there any patch in the works for this? we currently can’t import particle stacks which is a bit of a limitation, but it seems there is no way to downgrade to the previous patch without breaking things? Just wondering if I should bite the bullet and reinstall or wait for a fresh patch
Thank you for reporting, and sorry for any inconvenience. This is indeed a bug that was created by the patch- we will release a fix for this in the next patch tomorrow.
In the meantime, we have removed the patch from the list of patches that can be applied.
You can roll back the updates from this patch by running cryosparcm patch --force