Should I retry create_project after a timeout or lost response? #82
|
If project creation times out, can I repeat the same name safely? What can I recover if the response containing credentials was lost? |
Replies: 1 comment
|
Do not retry blindly. MCP After an ambiguous response, call A successful creation response returns the generated project ID, OTLP endpoint and ingest headers, plus a Sentry DSN and any required backend Sentry headers. Save those credentials securely when you receive them. Listings intentionally omit credentials, and an ingest secret is stored only as a hash. There is no public credential-recovery or rotation tool. Finding a project in a listing cannot reconstruct a lost creation response. Registering another project establishes a new identity; it neither recovers the old credentials nor replaces the old project's evidence. There is also no public project-delete endpoint for tidying up an accidental duplicate. Keep creation behind explicit approval and exclude it from automatic retries intended to shrink oversized read responses. If another project is necessary, make that a deliberate decision with the operator. |
Do not retry blindly. MCP
create_projectand HTTPPOST /api/projectsare non-idempotent: every successful call creates a separate project, even when the name and options are identical. A timeout does not prove creation failed.After an ambiguous response, call
list_projectsorGET /api/projectsand inspect the records before deciding whether another creation is appropriate. A name match can help identify a record, but repeating a name is allowed, so it is not an idempotency key or proof that a particular request created it. Follow listing pagination as needed.A successful creation response returns the generated project ID, OTLP endpoint and ingest headers, plus a Sentry DSN and any requi…