Retry and share knowledge from chat

Select your mailbox in Complexity and enable the required knowledge tool. Retry requires an active verified Microsoft mailbox binding. See Microsoft setup. Share actions resolve the current persisted mailbox binding and current library share access. A login alone does not establish that binding.

retryKnowledgeFile queues a fully uploaded failed file again. It needs current library manage access, knowledge.files.retry, the matching management permission, a separate grant, and MailGen license. Repeating the same request does not create a second parallel job.

listKnowledgeGroupShares, saveKnowledgeGroupShare, and deleteKnowledgeGroupShare handle current group shares with separate grants. Reading shares needs knowledge.shares.read at BFF and knowledge.share at AdminService. Changing shares needs knowledge.share. All share actions require current library share access.

Read-only document access is insufficient for retry or sharing. A saved share can grant only rights the actor currently holds. The five rights are read, manage, search, share, and useInAutomaticEmail.

A retry can incur another embedding charge. Inspect the file's processing state until ready. See knowledge processing and access.