---
title: Global Settings — Failure Handling
description: "The **Settings** tab (GravityOps → Asana → Settings) holds plugin-wide options that apply to every feed. Today it covers **failure handling**: where the \"Task Creation Failed\" backup task goes when automatic task creation cannot complete. These options are global on…"
url: "https://brightleafdigital.io/docs/global-settings-failure-handling/"
updated: "2026-11-15"
category: Integrate Asana with Gravity Forms / Settings Reference
---

# Global Settings — Failure Handling

The **Settings** tab (GravityOps → Asana → Settings) holds plugin-wide options that apply to every feed. Today it covers **failure handling**: where the "Task Creation Failed" backup task goes when automatic task creation cannot complete.

These options are global on purpose. They are deliberately kept separate from individual feed settings so that a feed whose project or assignee has been deleted (a common cause of failures) cannot also break the safety net meant to catch that failure.

---

### Fallback project

- The Asana project the backup **Task Creation Failed** task is added to.
- Putting every backup in one fixed project keeps these notices findable instead of floating loose in someone's task list.
- **Do not** point this at a project that a feed actively uses — if that project is the reason a task failed (renamed, deleted, access lost), reusing it would just fail again.
- If left blank, the backup task is created in the connected account's workspace without a project.

---

### Fallback assignee

- Who the backup task is assigned to.
- If left blank — or if the chosen user is later removed from the workspace — the backup falls back to the **connected Asana user**.
- Assignment is best-effort; the **fallback project** is what guarantees the task can be found, so set a project even if you leave the assignee blank.

---

### Notes

- The dropdowns list the projects and users the **connected Asana account** can access. Connect on the **Connection** tab first if the lists are empty.
- The backup task is created defensively: if the configured project or assignee no longer exists at the time of a failure, the plugin degrades gracefully (connected user, no project) so the notice is never lost.
- Recent failures are also surfaced in the **Asana Integration dashboard widget**, and the technical error is recorded on the Gravity Forms entry. See **Troubleshooting → Task Creation Failed → Backup Task Behavior**.

## Stuck? Ask in GravityOps Help

Search past answers or post your question, tagged "asana".

- [Integrate Asana: a "Task Creation Failed" task appeared instead of the real one](https://brightleafdigital.io/community/gravityops-help/4143/)GravityOps Help - 0 replies - 2 weeks ago
- [Integrate Asana: a project, section or assignee is missing from the feed drop-downs](https://brightleafdigital.io/community/gravityops-help/4142/)GravityOps Help - 0 replies - 2 weeks ago
- [Integrate Asana: pull Asana projects, users and tasks into form field choices](https://brightleafdigital.io/community/feature-requests/4137/)Feature Requests & Roadmap - 0 replies - 2 weeks ago

[Ask in GravityOps Help](https://brightleafdigital.io/community/gravityops-help/?gofrm_tag=asana)[Open a support request](https://brightleafdigital.io/support/)

GravityOps Weekly

[This iframe contains the logic required to handle Ajax powered Gravity Forms.](about:blank)
