-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
@mgz513 - Thank you for the feedback and I'm sorry for the trouble it's caused and the lack of visibility into what's happening. I've dug into the backend and it's revealed a few scenarios in which the connection could fail due to edge cases that weren't accounted for originally. With more information, I might be able to better pinpoint the exact issue that caused the failure, but I suspect it might have been the case that the file was duplicated, in Draft mode, or otherwise not saved to Figma cloud. This investigation has revealed a solution as well as inspired a more robust architecture to account for the various scenarios. I'm implementing this now and will be published in the next minor release. I'm also working to enhance the UX by providing more detailed information if failures occur and steps to resolve them, fix the overlapping toast message interaction sin, update the written documentation, and will plan to create video instructions to make the experience easier to use from the start. I am happy to hear that this plugin will address your needs and I want to make sure we get it working for you and others who might have run into this same headache! |
Beta Was this translation helpful? Give feedback.


@mgz513 - Thank you for the feedback and I'm sorry for the trouble it's caused and the lack of visibility into what's happening. I've dug into the backend and it's revealed a few scenarios in which the connection could fail due to edge cases that weren't accounted for originally.
With more information, I might be able to better pinpoint the exact issue that caused the failure, but I suspect it might have been the case that the file was duplicated, in Draft mode, or otherwise not saved to Figma cloud.
This investigation has revealed a solution as well as inspired a more robust architecture to account for the various scenarios. I'm implementing this now and will be published in the next min…