Troubleshooting

The agent's proposal was refused

propose_record and the other write tools need the propose permission. A read-only connection can read everything its owner can, but cannot propose.

Why it happens

The token was created read-only, or the OAuth connection was approved without the propose permission.
The person behind the connection is a viewer in the solution; proposing needs a role that may edit.
The solution's proposal limit was reached: agents may add at most 30 records per solution per hour. Review the open proposals and try again later.
No initiative could be found for new work or a requirement without a parent. It goes to the named initiative, else its parent's, else the session's choice, else the only open initiative besides maintenance. With several open initiatives and no choice, the tool refuses; defects go to the maintenance initiative unless one is named.
The solution's no work without a demand gate is enforced and the work's initiative answers no demand, so the work cannot move to Ready or straight to In progress.

Create a new token with propose ticked, or reconnect OAuth and grant propose on the consent screen.
If you are a viewer, ask a solution admin for a role that may edit.
For a missing initiative: tell the agent which one, or let it call select_initiative (the choice lasts 12 hours). get_agent_policy lists the open initiatives at session start.
For the demand gate: a person with portfolio.manage links a demand to the initiative on the Portfolio board.