I've been evaluating Recraft for the past two weeks for potential use in our HR department's internal communications and training materials. Overall, the platform is impressive, but I'm running into a persistent technical issue that's hindering my workflow assessment.
Specifically, the 'Regenerate' button frequently becomes unresponsive. The interface freezes completely after clicking it, requiring a full page refresh to continue. This happens under the following conditions:
* After generating an initial image variant.
* When using the 'Make Variations' feature on an existing graphic.
* It occurs in both Chrome (v124) and Firefox (v127) on a corporate machine with ample resources.
I've documented my steps to see if there's a pattern:
1. Generate a simple icon set based on a text prompt (e.g., "onboarding checklist icon, flat design").
2. Select one output and click 'Regenerate' for that specific image.
3. The loading spinner appears briefly, then the entire UI locks. No network activity is shown in DevTools after the initial request.
Has anyone else encountered this? I'm trying to determine if this is a known bug, a local configuration issue (perhaps related to corporate firewall or security settings), or a limitation of my trial account tier. A reliable regeneration function is critical for our use case, where we need to iterate quickly on benefits brochures and policy infographics.
That's an interesting pattern you've documented, particularly the part about DevTools showing no network activity after the initial request. It points to a frontend state management deadlock rather than a simple API timeout.
Given it happens across browsers after specific triggers like 'Make Variations', I'd suspect the issue is with how the client-side application is handling the promise chain or event loop when queuing multiple generative operations. Some of these design tools use a websocket connection for real-time updates, and a stale or unacknowledged message can block the UI thread entirely.
Have you tried inspecting the browser's memory heap snapshot during the freeze? I've seen similar lockups in other canvas-heavy apps when the garbage collector gets blocked by unresolved image buffers or Three.js contexts. A page refresh clears the entire context, which aligns with that hypothesis.
Boring is beautiful