Publiqa 1.0.15: Better Radar Suggestions, Brand Timezones, and Studio Approvals

1.0.15 is out.

Mostly edge cases this week, but they're the kind that bite once your workspace runs on autopilot. You shouldn't have to babysit timezones for an offline job. A single 404 shouldn't blow up a thirty-page radar scan. And you definitely shouldn't need to jump through three different pages just to approve a draft.

Here's the rundown.

Radar suggestions now read live web data

Radar used to rely on static knowledge. If a topic broke yesterday, the suggestion box didn't know about it yet.

Now it taps live search signals. We run queries in tight batches—five at a time, thirty results max. That gives you current talking points without chewing through credit balances.

We also patched the scraper. Previously, if one URL in a multi-page crawl returned a 403 or timed out, the whole job died. Now the crawler logs the bad link and keeps going. Simple, but it saves entire scans.

Persistent brand timezones

When you're logged into Publiqa, your browser tells us your offset. That worked fine until people started letting autopilot run overnight.

Without an active tab, background scheduling had no clean way to know where your audience lived. Morning posts occasionally slipped into 3 AM slots.

Brands now have their own timezone setting.

We detect it on setup, but you can change it anytime to Europe/Berlin, America/Chicago, or whatever matches your audience. Scheduled jobs, recurring drops, radar conversions—they all anchor to this setting now, even with your laptop shut.

Smart schedule stops crowding the same hour

Drop four platform forks into the scheduler at once, and they used to land on the identical minute if their platform defaults coincided.

The scheduler now checks your brand's calendar first. It looks at what's already booked over the next month and spaces posts across open days. Your LinkedIn and X followers won't get hit at the exact same second anymore.

Approve drafts without leaving the Studio canvas

Forks built by Autopilot or Radar start in an approval queue by design. You want human eyes on them before anything goes live.

The problem was the workflow: you had to exit the Studio, find the item in Planner, approve it, and come back.

We cut those extra steps out.

You can approve items right on the canvas card now—there's a green button right by the status tag. The inspector drawer has an approve button in its toolbar, too. If the whole batch looks good, click "Smart Schedule" in the canvas header. It grabs all your ready drafts, approves them, and places them onto your calendar in one click.

Safety checks for unlinked social accounts

If an autopilot run produces content for a platform you haven't connected yet (Threads, for example), we automatically disarm auto-publishing on that fork. A banner in your Planner points out the missing account so you can hook it up before post time.

We also baked in official API rate limits across supported networks. Heavy scheduling won't trigger account flags or rate throttles.

Asset verification and automated job recovery

A campaign won't jump into scheduling until every asset is rendered and saved. If video processing takes a couple of minutes, the campaign waits. No half-finished drafts end up on your calendar.

To keep queues moving, an automated monitor now watches for interrupted tasks. If a server deployment drops an active render, the system catches the orphaned job and resumes it on its own.

A few new notifications

We wired up alerts for events that actually warrant an interruption:

• A notification when an autopilot campaign finishes and lands on your calendar.
• An alert the second video renders or slide visuals are ready.
• A reminder when a scheduled post is coming up on an unlinked account.
• Direct notices for subscription renewals and failed card charges.

The update is already live in your account. Hop into Brand Settings to verify your timezone, or give the new Radar suggestions a spin.