Changelog

AFP publishes release notes inside the app, in the Updates section. That list is the record of what shipped and when.

These docs are not versioned. Every page describes how AFP behaves right now, and a page is rewritten on the day the behaviour it documents changes. There is no “docs for version 3.2”, because there is only one AFP running and you are always on it.

Where to look

You want	Go to
What changed in the product	Updates, inside AFP
How something works today	Any page in these docs
Why a campaign stopped doing what it used to	Why is my campaign not replying?
To report a release that broke something	Get help

After a release

Most releases add or change something in the interface, and campaigns that were running keep running. Two things are worth checking anyway, because both fail quietly rather than visibly:

• Executions. Open the campaign and read its execution list. An execution that ended in an error names the node it failed on, which is much faster than guessing from the outside. Test and debug campaigns covers how to read that list.
• Connected pages. A Facebook or Instagram token that expired during the same week looks exactly like a broken campaign from the outside, and it is by far the more common of the two. Connected pages shows which profiles need reconnecting.

If something that used to work no longer does, open a ticket before rebuilding the campaign. Include the campaign name and roughly when it last worked. That pair is usually enough to find the cause, and rebuilding first destroys the evidence.

No feed

There is no RSS feed, no Atom feed and no email digest for releases.

Notifications about your own account are a separate system: an expiring token, a campaign that is failing, a subscription about to lapse. Those are worth turning on, and they are configured per channel. Notifications covers what AFP sends and where it can send it.