Request Failed on Claim Transaction in ArcBlock Main Chain

I found an issue when checking another user’s transaction on the ArcBlock Main Chain Explorer. In the transaction details view, the Claim Transaction status shows “Request Failed”, even though the transaction is already recorded in block (#396) with a clear protocol fee. This creates confusion because there is no further explanation whether the failure is caused by the bridge, insufficient gas fee, or a synchronization bug between the explorer and the backend.