Task Creation Failed → Backup Task Behavior

When the integration cannot create the primary Asana task, the plugin follows a predictable fallback flow so you don’t lose context.

Event Flow #

1. Entry note added to the Gravity Forms entry indicating an error.
2. Backup task attempted in Asana.
3. If backup succeeds:
   • Another entry note is added with a direct link to the backup task.
   • Any notifications tied to Backup Task Created are sent.
4. If backup fails:
   • Another entry note is added with the backup attempt error.
   • Any notifications tied to Backup Task Creation Failed are sent.

Backup Task — Exact Details #

• Name: Task Creation Failed
• Assignee: the connected Asana user (the account used to authenticate via OAuth)
• Due date: today (same day as the failed attempt)
• Project: none (task is created in the connected user’s default workspace, not added to a project)
• Description:
  • Includes all mapped task values the original task would have received (name, description, assignee, due date, project/section, tags, custom fields, etc.)
  • Includes the reason for the original error

Where to See the Details #

• Gravity Forms → Entries → (Entry): review the entry notes for the initial error and the backup results (with a link if created).
• Asana: open the backup task (if created) and review the description for the copied payload and error reason.

What to Do Next #

1. Read the error — it will appear either in the entry note (if the backup also fails) or in the backup task description (if the backup succeeds).
2. If you can fix the issue, manually create the desired task in this one‑time instance based on the backup task or entry data.
3. If the problem can’t be resolved or persists, enable Gravity Forms logging (Forms → Settings → Logging) and contact support with:
   • The error text from the entry note or backup task and logs from the Asana Integration plugin.

Common Causes to Check

• Permissions / Access: connected user lacks access to the selected project/section/assignee/tag/custom fields
• Malformed rich‑text / merge tags in the task description
• Invalid field values (e.g., wrong enum option, date formats, custom field mismatch)
• Disconnected / expired OAuth or API limits