- The teammate's output was truncated by length and the cut landed mid-structure (mid-table, mid-link).; The brief asked for a format the deliverable surface doesn't render the same way (markdown vs. plain text, for example).; A file was generated but the upload to storage finished after the task po

1. Refresh the task thread once — files that looked broken on first load often appear correctly a few seconds later. 2. If a table or list looks mangled, reply: "Repost just the table, cleaned up." The teammate will reformat without redoing the whole task. 3. If a file won't open, ask for a differen

Task output looks wrong

What's happening The task finished, the answer is roughly right — but the output itself looks broken: a table is mangled, a chart didn't render, a link points to nothing, an attached file won't open, or formatting collapsed mid-page.

Why it happens

The teammate's output was truncated by length and the cut landed mid-structure (mid-table, mid-link).
The brief asked for a format the deliverable surface doesn't render the same way (markdown vs. plain text, for example).
A file was generated but the upload to storage finished after the task posted, so the link briefly looks broken.
The deliverable opened in a viewer that doesn't support the format (a .csv opened as plain text).

What to do

Refresh the task thread once — files that looked broken on first load often appear correctly a few seconds later.
If a table or list looks mangled, reply: "Repost just the table, cleaned up." The teammate will reformat without redoing the whole task.
If a file won't open, ask for a different format: "Send this as a PDF instead of a doc."
If a link is dead, post: "That link 404s — re-attach the file." The teammate re-uploads.
If none of this works, message Astra and she'll loop in support.