Is this the right issue type?
Summary
If the client code has to stop running (e.g., auth failure, connection failure), the task is orphaned and can't be picked up again.
Should include polling, caching data, and aggregation.
Separate submission from polling and retrieval.
Acceptance Criteria
Tasks
Confirm creation
Is this the right issue type?
Summary
If the client code has to stop running (e.g., auth failure, connection failure), the task is orphaned and can't be picked up again.
Should include polling, caching data, and aggregation.
Separate submission from polling and retrieval.
Acceptance Criteria
Tasks
Confirm creation