running a prompt took over 40 mins building on claude

anasbinti

Junior Member
Joined
Feb 8, 2024
Messages
129
Reaction score
32
guys i'm building a social media automation using claude with minimax m3 model since it's free on GMI these unti 4 Aug i guess, a prompt took over 40 mins is that normal and still not completed and keeps trying after fail and building and so on, i'm not if that's normal in these cases and how you build, btw i keep always reading what's coming an output and giving some details during the debug and creation process
 
You should try to reconstruct the prompt from the backups and structure it in modules. I suppose that prompt is huge, fact which will burn the credits very fast.
 
You should try to reconstruct the prompt from the backups and structure it in modules. I suppose that prompt is huge, fact which will burn the credits very fast.
yes the only part here i'm enjoying that there's no API limits for this case since the model is free to use, but what you mean by structure it in modules
 
yes the only part here i'm enjoying that there's no API limits for this case since the model is free to use, but what you mean by structure it in modules
Like, any project have more parts:
part 1, which do this.
part 2, which do that.
And so on.
By structure it by parts and build it module by module, the prompt will be splitted in parts (modules) and not by entire project.
I hope makes sense.
 
Like, any project have more parts:
part 1, which do this.
part 2, which do that.
And so on.
By structure it by parts and build it module by module, the prompt will be splitted in parts (modules) and not by entire project.
I hope makes sense.
yes, informative actually, i was dumping just to create a whole flow for the signup, long prompt but not enough details which makes it difficult to handle, i will start composing the flow right now step by step
 
i think you should try building it into smaller modules and testing each part before moving to the next, rather than letting one prompt run indefinitely. It’ll make debugging much easier and give you more control over the process.
 
Forty minutes usually means it's retrying a step it can't finish, not that the job is big. Splitting by module, as suggested above, removes most of it. The other half is making each step end in something checkable, a file or a test, so a failure shows up in seconds instead of after a long silent loop.

Best,
Floqal
 
Like, any project have more parts:
part 1, which do this.
part 2, which do that.
And so on.
By structure it by parts and build it module by module, the prompt will be splitted in parts (modules) and not by entire project.
I hope makes sense.
This. Ask Claude to create the project structure first and break the project down into different modules. Otherwise, you’ll keep running out of credits before you can finish the project.
 
Are you doing any orchestration
1 agent manages the pipeline
1 does the work
1 qa it and reports back etc
its proably getting looped and stuck somewhere along with a shit ton of content rot
 
Back
Top