Skip to documentation
DevelopersAvailable

Troubleshooting

Check the failed step before retrying the whole workflow.

The API rejects my key

Check the Authorization: Bearer header, whether the key has been revoked, and the required scope. MCP connections need distribution:read, and write tools also require distribution:write. Create a replacement key in Settings if you no longer have the token.

The agent’s work is missing

Check that the agent and your browser session use the same Kitmo account. The activity list shows the latest 50 recorded integration actions, and the plan list shows the latest 50 plans. Failed calls and an external agent’s unsaved work do not appear. Older actions may lack source metadata.

My plan says scheduled, but nothing published

Plan status and delivery status are separate. The current plan scheduling endpoints save the plan state without enqueueing delivery. Open the source content and schedule it in the composer, then track it in the queue.

One destination failed

Inspect that destination’s error in the queue. Reconnect the account if required, or correct the content to meet the network’s limits. Retry only the failed destination.

Reviewed against the implementation · 22 September 2026