@jc4p
this should be fixed now! the issue was the cancellation had happened onchain but wasn't reflected on the app's backend, i just deployed a patch for that + the app syncs with the chain every 5 min so it should hopefully have gotten its status updated
1 reply
0 recast
0 reaction