# Looking for ideas - how to solve 'create new card' button in a Swipe app **URL:** \ **Category:** Ask for Help\ **Created:** [February 19, 2021, 10:38am UTC](https://community.glideapps.com/t/looking-for-ideas-how-to-solve-create-new-card-button-in-a-swipe-app/23092 "2021-02-19T10:38:54Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [February 19, 2021, 5:30pm UTC](https://community.glideapps.com/t/looking-for-ideas-how-to-solve-create-new-card-button-in-a-swipe-app/23092/7 "2021-02-19T17:30:07Z")
> [@Rasha](#): > > I ask because it hasn’t for me. In fact, it stopped working in two of my apps last month. Per Support, use of compound actions for the purpose of clearing USP values following a submission **[1]** as well as setting columns through relations that are formed as a result of a preceding step in the same compound action **[2]** is not possible/does not work. Solving this would require significant time and resources according to Glide engineers. I’ve bumped into that. In my experience it works sometimes, but not all the time. I’ve long suspected that compound actions are prone to race conditions, and I [asked the question](https://community.glideapps.com/t/action-sequencing-blocking-or-non-blocking/19601) a while back, but never got a response. It’s good to have a definitive statement on it from Glide - now we know what to expect, and can build accordingly. --- _[View the full topic](https://community.glideapps.com/t/looking-for-ideas-how-to-solve-create-new-card-button-in-a-swipe-app/23092)._