Posts

Every post, from the moment its content arrives until it is published, with a row for each of its channels. This is the daily screen and the one you land on.

A post is one piece of content: everything one feed item, one custom feed event or one post from a post list produces, for every channel that listens to it. Each channel gets its own video, in its own shape and language, wearing its own brand, and its own row here. The channels of one post are still handed over together, in one email with one post kit and one webhook call. A repost is a post of its own.

It replaced four screens that each showed one stage of the same work. Following a single story meant jumping between them, and the point of Reelwire is to post, so the post is the row.

The posts are a list filed under their day: Today, Yesterday, then the date. Each row shows the clip's cover on the left (press it to play the video), what the post says, and under it the brand with its logo, the channel with its platform's logo, aspect ratio and language, and the content source with the icon its screen has in the menu and the time. On the right are its status, its three ways out as marks, where its review stands, Post kit, More and the tick. On a phone or a tablet the right part goes under the rest.

The figure at the top right counts the videos used this month against your allowance, because every channel of a post spends one. Its question mark takes you to Allowance. On Enterprise, a green line above the table says that priority rendering is on: your clips are rendered ahead of standard ones.

Following one post through

An event arrives from a feed, a post list or a custom feed. Every channel listening to that source becomes a channel of the post, and each is drawn in that channel's aspect ratio and language, wearing that channel's brand.

When the post is due it is handed over the ways each channel has switched on: by email to you, to your webhook for your own system or a posting service, or both. Whoever receives it posts it and says so, and only then does it read PUBLISHED. A channel with its platform connector on is posted on its platform by Reelwire itself, and reads PUBLISHED, with its link, once the platform has it.

The channels of a post that need no approval are handed over together, in one email and one webhook call, once every one of them is rendered and due. One still rendering holds the others back for at most 30 minutes; then they go without it, and it follows on its own. A channel that asks for approval is handed over on its own, once somebody approves it. See Channels.

Each row says when the post was created (or last moved, when the list is sorted by Last update), its status, the brand, the channel with its platform, aspect ratio and language, the content source with the feed, stream or post list it came from, where its review stands, and how its email, its webhook call and its platform connector went, explained below.

Status	What it means
ACCEPTED	The content is in and is waiting its turn to be handed to a render machine.
AWAITING RENDERING	In line to be drawn. Whether it waits in Reelwire's queue or at the render machine, it reads the same.
RENDERING n%	Being drawn right now. PRIORITY RENDERING means it was queued with priority rendering.
DOWNLOADING	Drawn, and being copied into your storage.
AWAITING APPROVAL	Waiting for a person to clear it.
SCHEDULED	Waiting for its time, or for the other channels of the post to be rendered, so they are handed over together. Nothing is wrong with a post that sits here.
HANDING OVER	Being handed over now: by email, to your webhook, through the platform connector, or several of them, as the channel says. Tried again on a set schedule if it does not get through.
HANDED OVER	Handed over, and not marked as published yet. Whoever received it posts it, then marks it as published: in the post kit from the email, here under More, or through the API.
PUBLISHED	Somebody said it is up, or the platform connector posted it. Where the post's link is known, Post kit has View the post.
SKIPPED	Handed over and deliberately not posted. It can still be marked as published.
UPDATING	A change to its text or video is being handed over, the ways chosen in Send update request. The post reads as before until it has gone.
DELETE REQUESTED, DELETED	Somebody asked for it to be taken down, and that was handed over. It reads DELETED once whoever posted it says it is gone, or the platform connector took it down.
REJECTED	Somebody rejected it, so it was not handed over.
RENDER FAILED, POST FAILED, UPDATE FAILED, DELETE FAILED	It stopped, and the row says why. RENDER FAILED is a clip that could not be rendered, which Retry rendering under More renders again. POST FAILED is a post that could not be handed over after every attempt, or that whoever posts it said could not be posted, which Change and resend under More puts right. A failed update or delete leaves the post as it was.
CANCELLED	Stopped before it was handed over: somebody pressed Cancel, its clip was deleted or removed to make room, or its channel was removed.

Hover a status for the same explanation in the product. On a failed one the hover also says why it failed, in the words it was refused with, a platform's own included.

Channel names the channel with its format, shape and language under it.

Under the status, a row on a channel that asks for approval says where the review stands: Approval after rendering while a post on a channel that asks for approval is still being drawn, then Approve and Reject while it waits for somebody who may approve (Awaiting approval for anybody else), then Approved or Rejected with who decided. A row on a channel that asks for no review says nothing about it. Both buttons ask once more before they act, because neither can be taken back. Approval comes with Small business and Enterprise. See Approvals.

Comments, a small link under the review and under More on every post, opens what people have said about it. An approver can press Ask for changes there to send a post back, and it reads CHANGES REQUESTED, with Rework post as a link under Comments, until somebody reworks it and it goes back for approval. See Asking for changes.

A change to a post that went out waits too, on a channel that asks for approval: the row reads Update awaiting approval, and the buttons ask Approve update or Reject update, showing the text and video the change would put out. Approved, it is handed over; rejected, the post stays as it went out. See Updates wait as well.

On Enterprise, nobody approves a post or a change they wrote themselves, and a channel can ask for two approvers: after the first, the row reads Awaiting second approval (or Update awaiting second approval) with the first approver's address under it, until somebody else approves. Both are set out under Approval rules on Compliance.

Three marks under the status say how each way out went, Email, Webhook and Connector in that order: coloured as the status would be where the way is on, an outline where it is off, and on hover the way and the word below. A post that also goes on to your syndication participants has a fourth, Syndication, which can be the only one in colour, since a post can go to them with the other three off:

It reads	What it means
Off	The channel does not have that way switched on.
Not yet	Switched on, and the post has not been handed over yet.
Sending (Posting for the connector)	On its way now, the first time or again.
Retrying	It did not get through, and is tried again on a set schedule.
Sent (Posted for the connector)	It got through: the email or the webhook call was taken, or the platform connector posted it.
Failed	It did not get through after every attempt. The row says why.

Filters answer from what is there

The period at the top opens on This week (Sun - Today), worked out from your own clock. A post is in a period when anything happened to it there, so one created last week and published an hour ago is in "Last 60 minutes". If something is missing, choose a longer period before anything else.

The State filter groups the statuses (Rendering, Awaiting approval, Scheduled, Handing over, Handed over, Published, Skipped, Failed, Rejected, Cancelled, and Deleted or delete requested), each with a live count of the rows in it, so "Failed (0)" says there are none. The Approval, Channel, Brand, Format and Content source filters offer only what the period holds. The search box reaches the caption, the channel, the brand, the feed, stream or post list, and the template. Sort by Created or by Last update.

The Archive filter shows the Active rows, which is where the list opens, or the Archived ones: the rows somebody filed away with Archive under More. It is the one filter with no "any", and whether a row is archived is not shown on the row.

The filters do not persist between visits. A filter left in place is the commonest way to conclude that your data has disappeared.

Post kit, and More

Every row has Post kit and More.

Post kit opens the channel's post as it goes out, with everything its post kit has for posting it, in the kit's order: a first card, Ready to post, as it reads now, with the two guides; then a card for each post. A post's card is headed by the channel, the platform, shape and language, its Status in the kit's words, and View the post once somebody gave the post's link. Under it, one under the other and each the card's full width: Share (on a phone or computer that can hand a file to another app; one press opens the share sheet), Download video, Download cover and Download text, which saves every text of the post as a JSON file; then the clip at its real shape; then Title and the title where the platform has one, and the text as it goes out, the caption with the brand's line, the link and the hashtags, each with Copy. A channel on No specific platform shows its text in every length, one for each kind of platform. That is the screen to check before approving something. It is greyed while there is no video to give: the post is still rendering, its render failed, or its clip was removed to make room in your storage (see Media).

At the top of Post kit, for whoever may change posts, is the address of this channel's post kit, the page the email's button opens, under Copy post kit link, to send by hand: to a colleague with no sign-in, or for a channel with its email off. It shows this channel's post alone, and whoever has the link can download the video, copy the text and mark the post as published without signing in. A link works for 14 days from when Post kit was opened, and only a post that has been handed over has one.

More holds the other actions, only the ones that apply to that channel, in four groups with a line between them. The first, on every channel, is Reuse: it starts again from what the post was made from, so a small mistake in a finished video is one change rather than the whole template filled in again. It asks which way:

• As a new post opens Add new post in a post list, already filled with the post's template, variant, build and content, every language included, and named "Copy of" the original. A post from a post list goes back into that list; one from a feed or an API stream goes into your first post list. Change what needs changing, then post it.
• As a video only opens Create clip with the same content, brand, shape and language, to render the video again and download it. Nothing is posted.

The original post stays as it is either way. Then what you say about the post:

• Mark as published says the post is up. It asks for the link to the post, which you may leave empty. With the link, Post kit has View the post, and any later update or delete carries it, so whoever posted it can find it again. A post that failed is not marked here: it is tried again with Resend post request, below.
• Skip this post says it was handed over and will not be posted. It reads SKIPPED, and it can still be marked as published later.
• Mark as deleted says it was taken down, once a delete was asked for.

Where the clip could not be rendered (RENDER FAILED), Retry rendering comes next and renders it again, from the post's content, brand and template as they are now, so a template or brand fixed in the meantime takes effect. Once the clip is there, the post goes on as it would have: to approval where the channel asks for it, then handed over when it is due, on its own if the post's other channels went out without it. It does not count as another video, since the attempt that failed was counted already, unless that attempt was refused because no videos were left this month: then it takes one now, and is refused while there is still none. On a paused channel, resume the channel first.

Then the requests Reelwire sends, each only the ways the channel has switched on, and never one that is off. Each dialogue lists those ways under Handed over by, with a switch each, every one on to begin with: switch off a way the request should not go. At least one has to stay on, or the dialogue's button stays greyed. A channel with Handed over by email and Handed over by webhook off whose posts go on to syndication participants still has all three: they then reach its participants alone, an update becomes the post's own at once, and a delete reads as requested. The ways you choose are the workspace's own; participants receive an update or a delete as before:

• Resend post request hands the post over again, as it reads now, the ways chosen: its email with a post kit, its webhook call with a new delivery id so the receiver acts on it again, and, through the platform connector, a repost: the video posted on the platform again as a new post. The earlier post stays there, and the post then carries the new one's link, so a later update or delete acts on the new post. On a post that failed (POST FAILED: its email, webhook call or platform connector never got through, or its receiver reported it failed), Resend post request tries it again: its post request goes anew, as the post reads now, the ways chosen, and the post moves on from failed as a first hand-over would. If every way fails again, it reads POST FAILED once more with the reason. Syndication participants are not sent it again: they had it the first time. On X, the platform connector reposts a post at most 2 times; after that, Reuse makes a new post, which counts as a new video. On a post that reads DELETED, in case it was deleted by mistake, Resend post request hands it over again as a new post while its clip is still stored, the ways chosen; through the platform connector it gets a new link, and on X it counts as one of the 2 reposts. Its syndication participants, who were told to take it down, are sent it again too.
• Change and resend is there on a post that failed (POST FAILED): the dialogue of Send update request on the post, opening with why it failed. What you save becomes the post, and its post request goes again the ways chosen, as Resend post request would send it, the platform connector posting it as a first post. It is how a post a platform refused is put right, such as X refusing a text over 280 characters. On a channel that asks for approval, the change waits for approval first, and goes once it is approved.
• Send update request changes its text or its video. See below.
• Rework post is there instead on a post that waits for approval or was sent back: the same dialogue, with nothing handed over, and the post goes back for approval. See Asking for changes.
• Send delete request asks for it to be taken down. See below.
• Cancel stops everything still to happen to this channel's post before it is handed over: a render in progress is stopped, an approval request is withdrawn, and it is not handed over. The post's other channels go on.

On a channel with the platform connector on, its mark stands beside each of the three requests. Solid means the connector can do this on the channel's platform, dashed means it cannot, and hovering says why. The dialogue then leaves the connector out and says what to do by hand. Where the connector is the channel's only way and cannot do it, the request is not offered; for a delete, Mark as deleted is there instead, for once you have taken the post down by hand. Posted by platform connector lists what each platform allows.

And last:

• Archive files the row away: it leaves the list and waits under Archived in the Archive filter. Nothing else changes, so a post still on its way carries on. On an archived row, the same place says Unarchive, which brings it back. Neither asks first, since either can be undone.

To archive several rows at once, tick the box at the end of each and press Archive selected under the list. Select all ticks every row on the page shown, Select none clears the ticks, and the ticks stay while you turn the pages. Under Archived the same button says Unarchive selected.

Mark selected as published, beside it, says that every ticked post that was handed over or skipped is up, after asking once. It goes without a link, since each post has its own: to give a post its link, mark it on its own under More. A ticked post that cannot be marked yet is left as it is and stays ticked.

Mark as published, Skip this post, Mark as deleted, Retry rendering, Resend post request and Cancel each ask once before they act, and Mark as published, Cancel and Mark as deleted cannot be undone. There is no separate Repost: sending a post again is Resend post request, which through the platform connector posts it anew. Post a video by hand goes through the email, the post kit it opens and each platform's steps.

More is offered only to somebody holding the Operations permission. A reviewer who holds Approvals and nothing else sees Post kit, and Approve and Reject on the channels waiting for them.

Updating a post that was handed over

Send update request opens the channel's post as it was handed over: its title where the platform has one, its video, its text, the brand's description, the hashtags and, where the platform posts one, the link. Keep the video, or upload or choose another from the media library to post in its place.

Send update request hands the change over the ways chosen under Handed over by, the dialogue's last section, of those the channel has switched on: its email goes as "This post changed", with a post kit holding the new text and, where you chose one, the new video, and your webhook receives the change; whoever posted it changes it there. A post the platform connector made has its text changed on the platform by the connector, where the platform allows it (Discord, Telegram, Facebook, LinkedIn and YouTube); on any other platform the connector is left out of the request, and you change it there by hand. On YouTube it changes the title too. On a Facebook Reel it cannot, which the dialogue says under Title: a title goes out only by email and webhook. A new video is refused on the post with what to do instead. The post reads UPDATING until the change has gone, and then shows the new text.

On a channel that asks for approval, the change waits for it. Send update request then hands nothing over: a note says the update waits for approval, and the row reads Update awaiting approval until somebody who may approve decides. Approved, it goes out the ways you chose, as above; rejected, the post stays as it went out. One update at a time can wait per post. See Updates wait as well. A delete request never waits.

The caption counter in the Send update request dialogue is not the platform's limit. It is the platform's limit less the brand's description, less the link with its text where the platform posts links, and less the hashtags unless this channel posts them as the first comment. On X a web address counts as 23 characters, as X counts it. Counted that way, a caption that fits here is not shortened on the way out.

Changing the brand description or the link in this dialogue changes this post only. It does not change the brand.

A channel on No specific platform has its descriptions in the dialogue, one per length: Tiny description (Pinterest, Threads, X), Short description (Telegram), Medium description (Discord, Facebook Reels, Instagram, LinkedIn, Slack, TikTok) and Long description (Facebook Feed, YouTube). A post handed over before the tiny length existed has the other three.

Deleting a post

Send delete request asks you to type the channel's name, then Send delete request again. It asks whoever posted it to take it down, the ways chosen under Handed over by above the name, of those the channel has switched on. Its email goes as "Please take this post down", with a post kit naming where it was posted where somebody gave the link, and your webhook receives a delete. A post the platform connector made is taken down on the platform by the connector, where the platform allows it (every platform but Instagram and TikTok, where the connector is left out of the request and you delete the post there by hand).

The channel then reads DELETE REQUESTED until the post is said to be gone: by the connector once it took it down, Mark as deleted in the post kit from that email, Mark as deleted under More, or your webhook's receiver reporting it. Then it reads DELETED. Where the delete could not be sent, it reads DELETE FAILED with the reason; take the post down by hand and Mark as deleted closes it.

On the platforms you connect by signing in, a post the platform connector made also reads DELETED by itself within a few hours of being deleted there, or of the platform taking it down, with no request sent and nothing to press.