Skip to main content
Last reviewed 25 July 2026, against v3.0.9. Each entry says how it was checked, because an entry that is quietly stale is worse than no entry: it tells you a working feature is broken.
There is no public issue tracker behind these yet. The repository has issue tracking enabled and nothing filed, so there is no thread to follow for status. If one of these matters to you, open an issue and it becomes the place this page points to.

​
Confirmed in the code

These were traced to the line that causes them.

​
DELETE /public/v1/posts/:id returns 500 for an id that does not exist

The handler looks the post up and then reads its group without checking it found one, so a missing id throws instead of returning a clean 404.
On the error text: it is a plain JavaScript TypeError about reading integrationId of undefined, not a Prisma error. Earlier versions of this page said Prisma, which sent people looking for the wrong signature.
Workaround: if your client treats “already deleted” as success, match on the 500 from this endpoint specifically.
Other 500s here are real failures, so do not swallow the status code generally.

​
PUT /public/v1/posts/:id/release-id can still return 500

The original cause is fixed: the value is coerced to a string now, so a non-string body no longer produces a data-validation error. What remains is different. The update matches on the post id, your organization and a release id that is not yet set, and when nothing matches, the database error surfaces uncaught as a 500. So you get it for:
  • a wrong id
  • a post in another organization
  • a post whose release id is already filled in
Workaround: confirm the post exists and has no release id before calling. Validating the body shape, which this page used to recommend, no longer prevents the common case.

​
An upload cannot be cancelled once it starts

The uploader is rendered with its cancel, pause and retry controls hidden, and there is no abort path behind them.
Workaround: let it finish, then delete the asset from the post.

​
Reported, not reproducible from the code

Real reports, but we could not confirm them by reading the source, so treat them as leads. If you hit one, the detail in an issue would let us fix it properly.
Reported as cannot read properties of undefined on the connect page. The code path was substantially rewritten since the report and now guards its response parsing, so we cannot point at a line.If it happens: retry, and if it persists, run the connect flow in a fresh incognito window.
Those are minified names, so there is nothing to search for without the original error and a source map.If it happens: start again from the channel list rather than refreshing the broken screen.
Session replay is on at full sampling, so the mechanism is certainly still there. Whether the overlay still appears on this page specifically, we could not confirm without running it.If it happens: ignore the overlay. The authorization usually completes anyway; refresh your channel list afterwards.
The component uses optional chaining broadly during load and we found no unguarded access that would explain it.If it happens: refresh once the data has arrived.
This one was previously attributed to Transloadit assembly expiry. That attribution looks wrong: the error text comes from the Veo3 generator path, which is a different provider entirely, so the old advice about shorter prompts does not follow from it.If it happens: retry. We would like a report on this one, because the cause is not what the page used to say.

​
Fixed since this page last claimed otherwise

​
AI image generation, Unknown parameter: 'response_format'

Fixed in May 2026. The parameter that newer OpenAI versions rejected was removed and the model updated. All three routes that were affected go through the same function, so all three are covered.
It is listed here rather than deleted because the page carried it for two months after the fix, and anyone who read it in that window was told to work around something that already worked. If you are on an older image than v3.0.9, upgrading is the fix.

​
Something not here?

​
Next steps

A post did not go out

The four states, the red badge, and how to send a failed post again

Uploads and media

Payload limits, video failures and the cancel-in-flight gap

Delete a post

The endpoint behind the first 500 above, and what it returns

Support

What to put in a report so the first reply is the useful one