Skip to main content
Requests and agent runs have different statuses and next actions. Check the original item before repeating work, especially when a second submission could create a duplicate task or message.

​
A request is missing

Open Tasks > Requests and check whether the item is pending, approved, or rejected. For attendance, a day marked Not sent is still on the employee’s time card; they need to correct and Save it before review. A rejected time off request is final, so the employee must create a new one. A rejected expense can be corrected with Edit & resubmit.

​
A specialised agent stopped

Open Agents, select the saved agent, and inspect its Run history. Needs input to start means the run is waiting for an answer. Needs action can point to a missing permission or connection. Read the specific request before replying or granting access. This run could not be planned means no step was created; inspect the details and use Try again if appropriate.

​
A Chat action is waiting

Return to the main Chat conversation. The agent may have proposed an action that needs confirmation or asked you to connect an account. Check the proposed details before continuing. Once a request or run finishes, inspect the affected record or external destination to confirm the work occurred.

​
Next steps

Requests and approvals · Agent run history · Review Chat actions