Lindy Community Icon

Infinite Credit Bug: Test Runs Won't Abort and Burn Credits

·
·

*Infinite Credit burning bug* Has anybody ran into an issue with a test run being UNABLE to abort a test and burning up ALL your credits? This seems like a major bug. My expectations are; if you try a test run and hit an error - the test should automatically stop/pause. At the very least... I should be able to easily and reliably stop it myself. Neither or these were true in my scenario. I hit an error early in my workflow - I think even within the free 500 credit test (or jsut after that point)- but then the test just kept going... get this - even after I deleted the whole task. I tried:

  • hitting stop on the main task & sub task

  • typing 'Stop' 'abort' etc in the chat.

  • Then eventually (seeing my credits burn away) I just deleted the whole task (assuming that surely will stop the task)

but no... it just kept going and burning up all my credits. Please help! This is a critical issue that prevents me from investing into Lindy. Positive note: my experience with support so far has been very positive. I am still highly motivated to build with Lindy - but this is a critical blocker that I'll need support with. Has anybody else experienced this or have any solutions?

  • Avatar of Mia B.
    Mia B.
    ·
    ·

    Hi Trevor M. try control, option, click on the task that's spinning. It'll bring up a menu and you should be able to stop the task. If that doesn't work the same menu will give the option to delete it. Hope that helps! 🙂

  • Avatar of Ty B.
    Ty B.
    ·
    ·

    I had this issue when I was on free, but when I run tests I don't get charged for my normal credits. It says there's 500~ test credits available and if you go over that it starts eating into your normal credits. None of my tests have gone over the 500 test credits and eaten into my normal paid credits. Only when I run a task when it's enable do I have my credits eaten.

  • Avatar of Trevor M.
    Trevor M.
    ·
    ·

    Mia B. Thank you very much for your reply. I believe I did try this. But I'll try again next time and report back. Still, none of the other methods worked either - even deleting the entire sub & parent tasks. I really hope those are on the dev teams radar!!