Hey, thanks for the report. “An unexpected error occurred” is a generic fallback we show when the server doesn’t return a specific error message, so we can’t trace the root cause from that alone. On your account, Composer 2.5 Fast requests are completing successfully, so this looks like a one-off glitch.
If it happens again, we’ll need a couple things to investigate:
The full error text. Expand the error message, it usually includes details like PING timed out, Blob not found, connection error, etc, and send a screenshot.
The real Request ID: chat menu (three dots in the top right) > Copy Request ID. What you sent is a generation UUID, not the server-side ID.
Whether it reproduces consistently or it was just a single occurrence.
If it hasn’t happened again yet, it was most likely a transient issue and retrying the request should be enough. Let me know if you can reproduce it and we’ll dig deeper.