How Feeds Run

When a form is submitted, feeds are processed in a predictable order. Each feed is evaluated and, if its conditions are met, the integration attempts to create or update a task in Asana.

Feed Lifecycle #

1. Entry submission → Feeds are evaluated in the order they appear.
2. Conditional logic check → If enabled, only feeds whose conditions match will run. All feeds without conditions run every time.
3. Task creation → The plugin attempts to create/update the task in Asana.
4. Entry notes created → For every successful task (or backup task), an entry note is added to the Gravity Forms entry with a direct link to the task. Entry notes also log errors and other significant events.
5. Notifications sent → You can configure notifications to trigger on these events:
   • Task Created
   • Backup Task Created
   • Backup Task Failed

Error Handling and Backups #

• If a task cannot be created, the system attempts to create a backup task instead.
• Backup tasks:
  • Are due the same day
  • Are assigned to the connected Asana user
  • Do not appear in a specific project (default workspace only)
  • Contain the original task details and the reason for the error in the description
• If the backup task is created successfully, an entry note with its link is added and the Backup Task Created notification can fire.
• If even the backup fails, an entry note logs the failure and a Backup Task Failed notification can fire.

Notifications and Merge Tags #

• Notifications can include a merge tag that inserts the task link directly into the message.
• This is especially useful for backup tasks since they are not tied to a project and may otherwise be harder to find.

---

In short: feeds run in order, each success or failure is logged in entry notes, and notifications keep your team informed with links directly to the created or backup tasks.