submitted is the initial state of every A2A task immediately after tasks/send is called. The server has received and acknowledged the task but has not yet started processing it. The task is in a queue or pending assignment.
Description
Every A2A task begins in the submitted state. The client receives this state in the synchronous response to tasks/send before the remote agent begins any work. From submitted, the agent transitions to working when it begins processing.
If the agent cannot accept the task at all (capacity, policy), it may transition directly from submitted to failed without entering working. The submitted state is important for understanding task queuing: a large number of tasks sitting in submitted indicates the remote agent is at capacity.