@ShashiBhushanYM Thanks for the additional info via DM. I'm not able to reply via DM, since we're not following each other. But I was able to locate and escalate your ticket on your behalf. The team should be in touch soon.
@ShashiBhushanYM Hi there, I'm Denise from the Community team at Figma. Our team here on X isn't able to assist with Account Management. Did you receive the reply from support last Wednesday, May 27 on ticket #1915172? Please DM, and we can try to get you connected with support. https://t.co/mYtUw4KJoq
Hey David, I'm Denise from the Community team at Figma. You can copy style properties using the keyboard shortcut (Press β₯ Option + β Command + C (Mac) or Alt + Ctrl + C (Windows) then Select the target element and press β₯ Option + β Command + V) or using the right-click menu > Copy/paste as > Copy properties. Right-click the target and choose Paste properties.
@madsmccaus Hey there, I'm Denise from the Community team at Figma. I hear you. This is something we've flagged to the team for reconsideration. Feel free to add your feedback here: https://t.co/eznkLAPcd2
@UMAD Hey there, I'm Denise from the Community team at Figma. As mentioned by Gayani, this is a bug that our team has been investigating and trying to fix. Hang in there!
@hunterthompson Hey there, I'm Denise from the Community team at Figma. Are you by any chance trying to find matching layers within the same frame? Or is this happening across different frames?
@toco_jpg Hey there, I'm Denise from the Community team at Figma. Are you still having issues submitting the form? If so, please feel free to provide more details via DM. https://t.co/mYtUw4KJoq
Hey there, I'm Denise from the Community team at Figma. This usually happens due to the JPEG compression. You can fix this by changing the document color profile to sRGB in preferences and setting the explicit export profile to sRGB as well. This should stop color desaturation or shifting for your JPEGs.
@joelnevius Glad to hear that, Joel! Figma relies on continuous background communication via Port 443 and WebSockets. Adding a new tab often creates new network routing demands that can be temporarily throttled or blocked by the VPN tunnel.
@RaziAns14640044 Hey Razi, I'm Denise from the Community team at Figma. This is usually caused by layer name mismatches. Check your layer tree in the main component and the instances. Ensure you haven't renamed layers, otherwise, the component will reset.
@bethanhelen8 Hey there, I'm Denise with the Community team at Figma. This sounds similar to a bug that our team is already investigating. Are you able to share more details via DM? https://t.co/mYtUw4KJoq
I hear you, Dillon. Is this happening when you're trying to login as well as when you're trying to use the mobile app? Can you please me a DM with your Figma account email address and more details? The mobile team wants to take a closer look at what may be happening with your account.
Hey there, I'm Denise from the Community team at Figma. Thanks for flagging this! This usually happens if they are flattened vectors, boolean group results, or special shapes (like instances) where certain constraints prevent editing. To fix this, you must select the specific vector points (Enter key) or use the corner radius fields in the Design panel.
@madamkruvasan Hey there, I'm Denise from the Community team at Figma. My team on X isn't able to assist with Billing. But please send over your Figma account email address via DM, so I can help connect you with our support team. https://t.co/mYtUw4KJoq
@araperezcast_ Hi there, I'm Denise with the Community team at Figma. Do you have a ticket number or your Figma account email address that you can provide via DM? I'd be happy to help get you connected with our support team. https://t.co/mYtUw4KJoq
Hi Manish, apologies for the delays, especially going into the weekend. The latest update is: an Account Executive is now assigned and actively reviewing your upgrade to Enterprise. As of today, theyβre working directly with the Sales team to move this forward.
Weβve followed up again to emphasize urgency and are continuing to track this closely. While response times may be a bit slower over the weekend, your case is actively in progress and not blocked.
Weβll share the next update on your ticket #1831706 as soon as we hear back.
@DocScrit Hi there, I'm Denise with the Community team at Figma. It typically takes a few business days to hear from our direct support team. It looks like support replied to your open ticket #1855912 today. Please check your email inbox to continue to work with support directly.