While maxinja works
After you send a brief, maxinja works on the campaign, template or workflow in your workspace. You can follow its progress, answer questions and refine the saved result. This page explains what happens when a request completes, changes direction or stops partway through.
Changes are saved as it works
maxinja saves changes directly to the campaign, template or workflow it is working on. There is no separate approval stage for each assistant edit. Ask for a draft when that is the intended result. A request to publish or send can perform that action, subject to the product’s validation, permissions and execution gates.
For a first campaign brief, include “leave it unscheduled.” For a workflow, include “keep it unpublished.” These describe the state you want maxinja to save.
| What happened | What to check next |
|---|---|
| maxinja saved a campaign draft. | Open its audience, email and schedule. Review the sender, offer and recipient previews. |
| maxinja saved a workflow. | Inspect its trigger, timing, branches and step configuration. Check whether it is published. |
| maxinja reports that a send or publication was requested. | Check the campaign or workflow state and its execution history. A completed assistant response does not establish delivery. |
| The request stopped or failed. | Open the saved item to see which changes completed before continuing. |
Following what it is doing
maxinja delegates campaign, template and workflow work to specialist agents. You see their jobs, progress updates and a report of what changed. A workflow specialist handles the journey and its emails together; a broadcast specialist handles the campaign and its email together.
For an audience, review the contact type, the condition in plain language and the matching people. For an email, inspect the rendered samples as well as the summary. Reports can identify incomplete work or unresolved requirements; use those to guide the next request.
Answering its questions
maxinja can ask for missing information or a decision during a task. The question appears in the conversation with its own input, and that is where your answer goes: the normal message box waits until you have replied.
- Some questions come with answers you click instead of typing.
- Some come with a countdown, and pick a stated default if you do not answer in time.
- Some ask for a file, or for you to point at something with
@.
One request at a time
One request runs at a time. A message sent while maxinja is working steers that active request. Name the correction and the part it changes: “Keep the offer fixed; only adapt the introduction.” If maxinja has asked a question, answer in that question’s input.
Steer, stop and retry with the saved state in mind
A correction takes effect when the running assistant reaches a checkpoint. It does not undo a change that has already completed.
| Action | Effect on the conversation | Effect on saved work |
|---|---|---|
| Send a correction while it works | Queues guidance for the active request. | Completed edits remain; the agent can use the correction as it continues. |
| Stop | Requests interruption and clears queued follow-up input. | Completed changes and external actions remain. |
| Edit and retry an earlier message | Removes later exchanges and runs the revised request. | Does not restore previous campaign, template or workflow versions. |
| Delete messages | Removes part of the conversation. | Does not undo changes or recall email. |
If the connection drops, reopen the chat and inspect its status and the saved item. Continue with a reference to that item and the missing change: “Finish the sender correction on this draft; leave it unscheduled.” Check uncertain send or publication outcomes before requesting the action again.
If maxinja reports a transcript limit, start a new chat and attach the existing item. If it reports a full input queue, wait for the queued input to be consumed before adding another correction.
Follow-ups keep working on the same thing
Once maxinja has built you a broadcast, the next request normally refines that same broadcast rather than starting a new one. When you do want a second one, say so: "now make a separate broadcast for the trial users".
Ask it questions about what it built, too. "Why does this workflow have two branches?" goes to the same specialist and comes back as an explanation, without changing anything.
Emails it writes for you
When the work is an email, maxinja writes the content, keeps a preview rendered from sample data, and looks at that preview to check its own work. It follows the selected brand kit for colors, fonts, and images.
If the email needs a picture your brand kit does not have, maxinja has two ways to fill the slot, and it chooses between them itself:
- A labeled placeholder. A stand-in that blocks out the slot at no cost. maxinja reaches for this while the layout is still moving, or when the picture is yours to supply.
- A generated image. A real image from the image model, on brand. This one costs credits.
To decide it yourself, say so in the request: “Use placeholders; I will add the images.” To replace one, add the intended picture to the kit’s asset collection and ask maxinja to use that asset.
Check what completion means
maxinja checks the saved result before reporting a completed change. A completed draft edit can still have unrelated draft issues; it does not mean the campaign was sent or the workflow was published. Confirm those states in the campaign or workflow itself, and use email or run history to inspect execution.
When something goes wrong
- A request fails. It is marked as failed with the reason. Nothing is rolled back: whatever was already built is still there, and a follow-up message can continue from it.
- Credits run out. maxinja checks your credit balance before it starts and again as it works, so an exhausted balance stops a run partway rather than at a tidy point. Top up, then ask it to carry on.
- You do not have write access. Workspace assistant commands and execution are refused. If access is removed during work, further execution is stopped; previously saved work remains.
Related
- maxinja: what it can and cannot build.
- Working with the assistant: the chat pane, references, and attachments.
- Broadcasts and templates: the things it builds most often.
- Adaptyle: the per-recipient personalization it writes into an email.