Lindy Community Icon

Credit Refund Request for Agent Builder Synchronization Bug | Lindy Community

Credit Refund Request for Agent Builder Synchronization Bug

·Oct 30, 2025 11:04 PM·

Credit Refund Request - Agent Builder Bug Hello Lindy Team, I would like to request a refund for the credits consumed during task ID 6903c6f33bb0d9afa97157ff (URL: https://chat.lindy.ai/raphael-machionis-workspace/lindy/chat-68421cb7c22d7402e81f5fc9/tasks?task=6903c6f33bb0d9afa97157ff). Issue Summary: While creating the "PPC Thievery" agent (Agent Definition ID: 6903c702b721054e1cd41b1a), the Agent Builder consumed an excessive amount of tokens (over 38,000 tokens) due to a synchronization bug between the backend and the Flow Editor interface. Technical Details: The agent was successfully created in the backend with 16 nodes and 16 connections (as per graph JSON ID: 6903ebfdd9a1a9ca1cd6c75b) The Flow Editor interface remained empty throughout the entire session, showing only "Select Trigger" Multiple attempts to refresh, switch tabs, and reload the page did not resolve the issue The AI Agent Builder continued consuming tokens attempting to fix reference and synchronization issues that were caused by an interface visualization bug Evidence: Chat URL: https://chat.lindy.ai/raphael-machionis-workspace/lindy/chat-68421cb7c22d7402e81f5fc9/tasks?task=6903c6f33bb0d9afa97157ff Agent URL: https://chat.lindy.ai/raphael-machionis-workspace/lindy/new-agent-4-6903c6812588409e7cf72c05/editor?newLindy=true&wiz=6903c6f33bb0d9afa97157ff Agent Definition ID: 6903c702b721054e1cd41b1a Graph ID: 6903ebfdd9a1a9ca1cd6c75b Request: I am requesting a full refund of the credits consumed in this task because: The agent was correctly created in the backend but was never visible in the interface Tokens were spent trying to resolve a platform synchronization issue I was unable to use or test the created agent due to the bug Thank you for your attention to this matter. I look forward to your response. Best regards, Email: raphael@assis.co Workspace: raphael-machionis-workspace

Montanha
·
·
Yaaj B.
·
·
Hey there! Looking at your chat and going to "Go to agent" from there, I can see this Agent with a fully built out agent in the flow editor!
Montanha
·
·
I understand you can see the flow on your side, however during my sessions the visual editor did not render anything and the agent did not execute tasks, while credits were consumed. I spent multiple sessions iterating with the agent that was supposed to create and run my flow, shared several screenshots of the visual editor rendering a blank canvas, and kept asking the agent to fix it. Despite that, executions kept consuming a large number of credits while producing no usable output, and today I hit my monthly credit cap. You can see in the conversation history that I repeatedly reported the blank editor and missing outputs. That combination makes this a categorical defect: the backend state existed, but the UI did not render and the agent did not deliver results while billing continued. This is unacceptable given the number of attempts and the clear evidence in the chat history. Please refund the credits from these failed runs, restore my monthly limit, and investigate to ensure the editor reliably loads and runs for the end user and that failed or no-output runs do not bill.
Ross
·
·
I have run into this too, where the interface is not showing the agent, but the agent is there. Solution, log out of Lindy, close the tab, log in again, the agent will be visible. Not a great workaround, but it does solve the problem. But, one time that did not work either. I had to delete the agent to get it to stop consuming credits.
🤕1
Montanha
·
·
Ross’s reply confirms this is not an isolated incident. The interface can hide an existing agent, yet executions still consume credits. Logging out and back in is not an acceptable fix, and in some cases even that does not work. In my case, before I could identify the platform bug, an additional ~2,000 credits were consumed with no usable output.
Montanha
·
·
Yaaj B.
Yaaj B.
·
·
Hi Montanha - sorry for the delay here, I've DM-ed you for a credit resolution 🙂