reminder if building on FC protocol -

client -> protocol has a time gap - an action on WC shows up on WC immediately but during times of heavy load, can take up to mins to appear on the protocol (this is expected and WC is usually pretty good)

worth keeping in mind when building frames that rely on quick actions

live example of this happening right now where data is appearing on the network in short bursts instead of in real time

building /neynar & /nfs 🪐 | neynar.com | writing bad casts on /rish 

solution: use a non WC client to post Frames?

Does this affect the ability for users to mint NFTs in the frame?

This would explain what I’m seeing in the UI/UX. After recast I have to wait a few minutes for the corresponding mint to work

I think this is the answer to a question I had.
So basically, the reason why some actions don't work is because the server hasn't processed the command yet, or rather, hasn't received the command yet.