Generated plan was erased
# bugs-forum
g
I got an error message in the epic saying the artifact timed out and now the plan that was generated, which again I clearly copied, is deleted. Unfortunately the error message is gone before I could copy it and paste it. It is seemingly waiting for execution, but this hands off to another agent to build, so what execution was it waiting on that timed out? The plan? It assumes the plan was skipped, but sometimes generate is there, and I press it and it works. Sometimes it is not, like if I do not generate a plan, it times out and I cannot generate one any longer. So this might be separate but in the 3rd and 4th image, they are different tickets that do not show the generate plan. Overall, when I copy a ticket, it will bring me to a screen where I can generate a plan for that ticket, a more detailed plan, I think, but it also allows me to then verify it. I like that workflow, using epics, and got used to it. The point is I would like to be able to have a ticket, I can generate 1 plan for and implement, then verify. I do not want to go to phases, as phases usually always generates more than 1 plan for a ticket. If the tickets are already separate and distinct, then creating 3+ phases with plans for them is overkill. I mean I have 27 tickets to get through. The other thing is, it will generate 3 phases or more regardless if it needs it or not. When they are separated into 27 tickets, I don't think I need another 3+ phases as well. https://cdn.discordapp.com/attachments/1469733503443927130/1469733503666098207/image.png?ex=6988bb7d&is=698769fd&hm=8faba9284955d094058a5eec930944e72d3535e068bef4d761db1be355fe098a& https://cdn.discordapp.com/attachments/1469733503443927130/1469733504047775785/image.png?ex=6988bb7d&is=698769fd&hm=2efcb89c80e0368c90cae42826958e25b44926c3a3bd4936f1c871161e35dd49& https://cdn.discordapp.com/attachments/1469733503443927130/1469733504467337227/image.png?ex=6988bb7d&is=698769fd&hm=76825b4979e311f050d52fdd9005022abccacefddd48f09497fefc6033b93989& https://cdn.discordapp.com/attachments/1469733503443927130/1469733504995692648/image.png?ex=6988bb7d&is=698769fd&hm=819ab22eb902ed10f5c3cc35668fc82358352d95b13244e74ef74b1e7781c4e1&
p
Thank you for bringing this to our notice. We are investigating this issue and will keep you posted on the updates.
To confirm the reproduction steps: 1. You are sending a handoff request for a ticket 2. Execution gets created and plan generation starts 3. Plan is generated 4. Plan gets erased and user query starts showing waiting for execution Please correct me any I missed some steps
Here is the error, I knew I would get it again, this was the error that erases whatever I have done in the epic. I had it generate a plan it erased and then I picked review, which it did, but warned me the plan was not generated (although it was as I showed above), and did the review. Then I got this error message and now its gone. https://cdn.discordapp.com/attachments/1469733503443927130/1469752370970886296/image.png?ex=6988cd0f&is=69877b8f&hm=e870a6f33cddc166924d58e39722a808eaf0660af9d05ec72ac57624cd0df9cb&
What is new is it is added to the executions.
2. I generate a plan
p
We are fixing the copy behaviour and should be fixed in upcoming release going out in next couple of hours
g
I figured that was not on purpose
however, I dont mind that as it was the only way to generate a plan from that ticket
without having to go to phases, that would generate 3+ phases for it.
So I could put this all into phases, and get 34 phases, or I could use epics, and get 34 tickets
I dont think I need 132 phases
So now it is putting it into execution, but what is it executing?
plan gets erased, seemingly because of the execution of something that times out.
I have waited for it to execute something, and seemingly nothing gets executed
So this is probably the fact the copy is broken
p
When you choose copy as a handoff option, it copies the prompt to your clipboard, which you can pass to your preferred coding agent by pasting. The user query remains in the execution state, waiting for the coding agent to trigger the completion signal once it has finished the implementation, so that Traycer's verification loop can review the changes.
I can understand the confusion this has caused. The copy should just copy the ticket content without triggering an execution. This is already fixed and will be released soon.
g
Yes it copies the path to that plan and the name, not the entire plan, but whatever.
And I have used those plans to build from
I would like to be able to verify them though, and the only way to do so is the way I found, or phases
However, when I brought 1 ticket into phases, it created 4 phases for it
p
Did you try the new
/execute
command we added after the ticket breakdown? It orchestrates ticket creation and triggers execution in batches based on dependencies. The AI would decide which tickets require additional planning beyond their content and continue the loop until all tickets are completed.
g
So I have not, as I am usually cautious of giving AI too much control without my intervention.
p
This will also trigger verification once the coding agent has implemented the changes, without you having to request it manually.
g
ok
so it basically handles handoffs
So executions are basically the YOLO feature
p
Yes, it handles handoffs by creating batches of tickets that can be implemented in parallel and follows the entire manual handoff flow. It can also course-correct the implementation done by the coding agent if it deviates from the defined specs.
g
Smart YOLO
p
Executions can be manual as well as Smart YOLO, which makes sure that the Epic is implemented end-to-end in a single go.
g
ok, yeah so in the execution, I should be able to plan and verify?
or use the yolo feature
Alright, I will trust your implementation and try to follow the intended workflow
p
Sure, we will also improve the manual handoff experience, which allows you to plan and verify.
It made another execution
p
And all these are happening when you just click on the Copy, right?
well the copy seems to create an execution
those are all created from using copy
I did not manually create any of them. Which I do not mind the automatic execution creation
that is helpful
but I get copy should probably not do that
p
Yes, that will be fixed in the upcoming release.
g
I do have the execution configured
not sure if that could be why
How would I add a ticket to the execution, by creating the execution? As using copy basically copies and pastes it into an execution. So its technically doing what I would do anyway
Otherwise I have to manually copy those details and add it to the execution, which seems to be what copy is doing.
p
While we fix this, you can use the
Add Execution
button by adding a query like: "Plan out implementation for @(select Epic > Current Epic you are in)'s ticket @(ticket you want to implement)". This will allow you to trigger plan generation and follow the same flow as per phase execution.
g
I guess the execution configuration is not working. Also, if I configure it with different providers, all I can do is applytoall to save. https://cdn.discordapp.com/attachments/1469733503443927130/1469760433761288254/image.png?ex=6988d492&is=69878312&hm=6aa32fefe3dc6e9580d4cad69beef6b495482bc29e62f921a1eb9b8d1556d7ac&
it doesnt save
if I apply to all, if I dont, if I check set as default, or not.
g
thanks!
p
Traycer v2.15.3 has been released with a fix for these issues. Please update the extension and let us know if the problem persists.
It has easy handoff options for Phases/Plan/Review mode and copy would just copy the ticket content.
3 Views