Skip to content

docs(connectors): status error code and how a block clears (PRO-2531) - #324

Open
adityamishra-hydradb wants to merge 5 commits into
mainfrom
adityamishra/pro-2531-error-classes
Open

adityamishra-hydradb wants to merge 5 commits into
mainfrom
adityamishra/pro-2531-error-classes

Conversation

@adityamishra-hydradb

@adityamishra-hydradb adityamishra-hydradb commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

FIX : PRO-2531

For humans

  • Get Connector Status documents error.code and error.failure_class, with a table of what each code means and what to do.
  • The docs now say how a block clears: a reconnect clears connector and resource blocks, and a successful sync clears a connector block.

The response schema on the page shows the new fields after CI regenerates openapi.json from the app PR hydradb-application PR 2514.

For agents

  • api-reference/v2/endpoint/get-connector-status.mdx, get-connector.mdx, update-connector.mdx: prose only. openapi.json is not edited by hand.
  • mintlify validate and mintlify broken-links pass.

🤖 Generated with Claude Code


Devin Review

bit2swaz and others added 2 commits October 20, 2026 00:40
…ears (PRO-2531)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Signed-off-by: bit2swaz <bit2swaz@gmail.com>
…k (PRO-2531)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Signed-off-by: bit2swaz <bit2swaz@gmail.com>
@mintlify

mintlify Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
cortex-ai 🟢 Ready View Preview Oct 22, 2026, 3:19 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@github-actions

Copy link
Copy Markdown

✅ Mintlify Hygiene

No issues found.

@openhack-agent

openhack-agent Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

✅ OpenHack Summary

Security review of docs(connectors): status error code and how a block clears (PRO-2531). 3 changed files; 0 findings at or above the low reporting threshold.

P1: Critical 0   P2: High 0   P3: Medium 0   P4: Low 0

Confidence Score: 5/5

No reportable security findings were detected in this scan.

Security merge-readiness rubric: 1 = critical, 2 = high, 3 = medium, 4 = low, 5 = no reportable findings. This score reflects scan findings, not a guarantee of correctness or complete coverage.

Files Needing Attention: None

Important Files Changed
  • api-reference/v2/endpoint/get-connector-status.mdx (modified)
  • api-reference/v2/endpoint/get-connector.mdx (modified)
  • api-reference/v2/endpoint/update-connector.mdx (modified)

Last reviewed commit: 7f8c54b · View review on OpenHack


TIP: Mention @openhack-agent in a PR comment to request a review or ask a question. Use @openhack-agent fix all for every finding, or @openhack-agent fix unresolved threads for open review threads only.

@openhack-agent openhack-agent Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OpenHack reviewed this commit. See the OpenHack Summary for the confidence score and fix actions.

@greptile-apps

greptile-apps Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The documentation changes appear safe to merge.

Summary

Documents connector failure codes and recovery steps.

  • Connector status pages explain failure codes and their next steps.
  • Reconnects clear connector blocks, while resetting a resource starts its sync over.

Both earlier, unnumbered findings are addressed: the page explains which settings reset and limits the fresh sync to filters.lookback_days. No new actionable issues were found.

Reviews (5) · Last reviewed commit: "chore: merge main into pro-2531 docs" · Reviewed by Greptile

greptile-apps[bot]

This comment was marked as resolved.

@adityamishra-hydradb

Copy link
Copy Markdown
Contributor Author

/devin review

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Starting Devin Review.

Devin Review

@devin-ai-integration devin-ai-integration Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.

Devin Review found 1 potential issue.

Devin Review

Comment thread api-reference/v2/endpoint/get-connector-status.mdx
…t delete-and-add resets (PRO-2531)

Delete and add again resets the resource: the sync position is empty,
and routing and custom_instructions that are not sent again change to
the connector defaults. Reconnect keeps them, so it is the first step.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Signed-off-by: bit2swaz <bit2swaz@gmail.com>
@adityamishra-hydradb

Copy link
Copy Markdown
Contributor Author

@greptileai review

@adityamishra-hydradb

Copy link
Copy Markdown
Contributor Author

/devin review

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Starting Devin Review.

Devin Review

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 new potential issue.

Devin Review

Comment thread api-reference/v2/endpoint/get-connector-status.mdx Outdated
Comment thread api-reference/v2/endpoint/get-connector-status.mdx Outdated
…only the lookback window (PRO-2531)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Signed-off-by: bit2swaz <bit2swaz@gmail.com>
@adityamishra-hydradb

Copy link
Copy Markdown
Contributor Author

@greptileai review

Signed-off-by: bit2swaz <bit2swaz@gmail.com>

# Conflicts:
#	api-reference/v2/endpoint/update-connector.mdx

This branch was successfully deployed

1 active deployment
staging — 7f8c54bd Deployed Oct 22, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants