While AdenAI is working: adding, cancelling, changing status

You have sent a ticket off, AdenAI has picked it up, and something else occurs to you. Or you notice that your job is not quite right as written.

Both are normal, and there is a way for both. Just not the same way at every moment.

A run has two halves

If your ticket says In progress, there is a second line next to the status at the top. It tells you which half you are in:

	AdenAI is planning	AdenAI is building
Adding something	yes, it goes into the same run	no
Cancelling the run	yes	yes
Changing the status	yes, applied after the run	yes, applied after the run
Archiving the ticket	yes, the run still finishes	yes, the run still finishes

Next to that line, half a sentence says what it means for you, and above the reply box it says so again at greater length. Both change on their own while you watch. You do not have to reload the page, and you are meant to see the window close rather than find out when you hit send.

While it is planning

AdenAI is reading up. It looks at your project and settles the steps it wants to take. Nothing in your project has been changed yet.

That is exactly why everything is still possible here. If you write a reply into the thread now, AdenAI collects it before it plans. It goes into the same run, and you pay nothing extra for it.

You get an immediate confirmation in the thread that your addition has arrived. That sentence is there for a reason: without it you only see your own text and have no idea whether it is still being read. Then you write it a second and a third time, and text sent three times costs three times as much.

Once it starts building

From here on AdenAI is writing code. Adding something is no longer possible. If you try, the page turns the reply down and says why. The text you typed stays where it is: you can send it as soon as the run is through.

The reason is not convenience on our side. An addition in the middle of the building would produce code that implements the old job for one half and the new one for the other. You cannot see that on a page straight away, and cleaning it up costs more than the ticket cost.

That is also the thought behind the whole thing: a job you have thought through pays off. The point is not to restrict you, it is that nothing half-baked ends up sitting in your project. What you decide before sending costs you nothing. What you decide afterwards costs a second run.

Cancelling

The button is called Cancel run and sits above the reply box for the whole run, in both halves. There is a confirmation first, and it tells you what the cancellation costs.

What happens:

• AdenAI stops as soon as the step it is currently on has finished. Not instantly, in the middle of a change, because that would be exactly the half-finished state the rule above is there to prevent.
• Whatever has been created up to that point stays. Nothing is lost.
• The ticket goes to Blocked. Not to Open, because then it would immediately queue itself up again, and cancelling is supposed to mean stopping.
• The progress is remembered. If you set the ticket back to Open by hand later on, AdenAI carries on where it left off instead of starting over.

Changing the status while it is running

You can also put the ticket somewhere else in the middle of a run. The change is only carried out once the run has finished, though.

There are two reasons for that. While AdenAI is working, In progress is the truth, and a ticket that says "Blocked" while something is being built for it is a display that lies. And: your change wins over the result. The ticket ends up where you put it afterwards, even if the run completed.

So that you are not left staring at nothing for two minutes after your own click, the line at the top says "Afterwards: ...", and a sentence about it goes into the thread.

A status change does not stop the run. If you want AdenAI to stop, you need the cancel button. More on the five states under Changing a ticket status.

Archiving a ticket while it is running

That works too, and here too the run that has started finishes and is charged. The result then lands in the archive, where you will find it again.

Because money is attached to it, AdenAI asks first in this one case, and the question tells you how far along the work is ("step 3 of 6"). At step 5 of 6 you decide differently than at step 1. With no run going there is still no question asked: archiving can be undone.

Two things that save you trouble

Waiting usually pays off. A run rarely takes long, and the time estimate at the top of the ticket is calculated from real runs. A reply to a finished ticket starts a new run, and AdenAI reads the whole thread along with it. So it knows what you are referring to.

You may close the tab. The run carries on on our machines, not in your browser. You do not have to sit in front of it.