The short answer
The optional Asana reference adapter projects Room contribution requests into an external work-management system. Delivery uses stable identity and bounded retry mechanisms. An external task remains a projection; it cannot automatically override the Room contribution lifecycle.
Separate the human assignment from its notification channel
A contribution request represents the work a person owes the Room. An external work-management task makes that request visible in another tool. Their delivery and completion states answer different questions.
The human work reference describes the optional OAuth-based Asana adapter and the application-owned delivery port. AgentPlat remains authoritative for the contribution even when the external system is where the person first sees it.
Stable external identity makes lookup meaningful
The documented delivery model includes idempotent enqueue, leased dispatch, provider lookup recovery and revision updates. These features address the case where a delivery attempt has an uncertain acknowledgement.
For an illustrative review assignment, the provider may create its task before the local worker loses the response. Recovery should use the configured stable identity and provider lookup path rather than immediately issuing an unrelated replacement task. Otherwise, one contribution can become multiple confusing assignments.
Bound retry behavior and expose unresolved delivery
The port includes bounded exponential backoff, attempt limits and explicit retry operations. Operators need to distinguish an assignment still waiting on a human from a delivery that never reached the external system.
The API reference documents revision and lease-token requirements for work-management retry. Re-read those current coordinates before deliberately retrying; a stale client should not take over dispatch based only on an old error message.
Keep completion in the Room lifecycle
An external task being marked done does not automatically validate the requested result or complete the Room contribution. The integration needs the appropriate identity, authorization and persisted transition.
The LiveView model can present contributions and external deliveries together. Preserve both statuses in the interface. “Delivered” should not become “completed,” and “retry pending” should not make the human's existing contribution disappear.
Validate only the integration you actually operate
Test a normal projection, uncertain acknowledgement, bounded retry and attempted unauthorized completion using an authorized development integration. Keep credentials and real account data out of retained public evidence.
The documentation treats live Asana validation as optional and separate from Room conformance. This article explains the reference contract; it does not claim that a live Asana account was exercised. Report the actual adapter, provider and environment used in your own check.
Sources and further reading
Documentation reviewed . Consult the linked documentation for current implementation details.