VAREXIS-INDEX ยท Free evidence

Connector sync and access evidence

25 source-linked reviews of distinct connector coverage, permission, cost attribution and trace-completeness decisions. Review dated sources and required evidence. Documentation does not establish live behaviour, authorization, settlement, deletion or certification.

Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.

Complete exact-ID manifest · Full catalogue · Existing MCP coverage

Can a Graph delta deleted-folder marker immediately remove the local folder

Can a Graph delta deleted-folder marker immediately remove the local folder?

Microsoft requires a local folder to be empty after all changes are synchronised before deleting it locally. A folder marker alone is not enough to decide what remains below it.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Reconcile child changes before deleting the local container; the marker does not prove physical erasure.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does renaming a Graph folder emit updated paths for all descendants

Does renaming a Graph folder emit updated paths for all descendants?

Graph documents that a folder rename does not return every descendant in delta, and parentReference.path is omitted. Clients should track items by identifier rather than infer unchanged paths from absent descendant rows.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Do not accept stale descendant paths as current locations without resolving their identifier hierarchy.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does an empty Graph sharing facet mean the item inherits its parent permissions

Does an empty Graph sharing facet mean the item inherits its parent permissions?

With hierarchicalsharing, Graph distinguishes inheritance from unique items with no sharing links using an empty sharing facet. The root of an unshared permission hierarchy can also carry that empty facet.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Interpret the requested header and hierarchy together; an empty facet alone is not effective-access verification.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does a non-owner Graph permissions response inventory every sharing grant

Does a non-owner Graph permissions response inventory every sharing grant?

Graph returns all sharing permissions to an item owner or co-owner, but only permissions applicable to a non-owner caller. A successful non-owner response is therefore a caller-scoped view.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Do not declare that no other sharing grants exist from a non-owner inventory.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Where should a Graph sharing review locate the source of an inherited grant

Where should a Graph sharing review locate the source of an inherited grant?

Graph sharing permissions can be direct or inherited. The inheritedFrom property identifies the ancestor supplying an inherited permission, so the child list alone is not a statement that the grant originated on that child.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Resolve the granting ancestor before recommending a scoped permission change; no change or revocation is performed here.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does one Graph message delta stream cover the whole mailbox

Does one Graph message delta stream cover the whole mailbox?

Message delta tracking is per folder. Microsoft requires each folder in a hierarchy to be tracked individually; completing one folder stream is not mailbox-wide coverage.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Keep untracked folders outside any completeness conclusion.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Can a filtered Graph message delta request establish complete coverage of a large folder

Can a filtered Graph message delta request establish complete coverage of a large folder?

The documented receivedDateTime filters on message delta return at most 5,000 messages. A time filter changes the coverage boundary and cannot be assumed to enumerate every matching message in a larger folder.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Do not accept an exhaustive export claim without accounting for the filter ceiling and source inventory.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does a created-only Graph message delta also prove that existing messages stayed unchanged

Does a created-only Graph message delta also prove that existing messages stayed unchanged?

Graph supports created, updated or deleted changeType selections. Selecting one change type limits the observed changes; the service carries the selection into continuation links.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Do not infer absence of updates or deletions from a created-only stream.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does Graph considering a webhook delivered prove the business action completed

Does Graph considering a webhook delivered prove the business action completed?

Graph treats a timely 2xx response as delivery. It recommends queueing a notification and returning 202 when processing cannot finish promptly, separating HTTP acceptance from subsequent application work.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Require queue and processing outcome evidence before declaring the downstream operation complete.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Can a responsive Graph subscription still have an unrecoverable webhook gap

Can a responsive Graph subscription still have an unrecoverable webhook gap?

Graph can delay slow endpoints and drop notifications for endpoints exceeding its documented timeout thresholds. Dropped notifications cannot be recovered through notification delivery, so restoring responsiveness does not prove gap closure.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Reconcile affected source changes independently before treating the capture interval as complete.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does restrictToMyDrive include every file visible to a Drive user

Does restrictToMyDrive include every file visible to a Drive user?

Drive documents that restrictToMyDrive omits changes outside the My Drive hierarchy, including application-data files and shared files not added to My Drive. Caller visibility and selected change coverage are different.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Do not treat this restricted stream as a complete inventory of accessible content.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Can Drive return file details for an item that has left the change corpus

Can Drive return file details for an item that has left the change corpus?

includeCorpusRemovals can include the file resource when it remains accessible despite leaving the change list. There may be no further change entries for that file in the selected corpus.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Do not assume continued monitoring from a last accessible file representation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Can a Drive client advance its durable change checkpoint while nextPageToken remains

Can a Drive client advance its durable change checkpoint while nextPageToken remains?

A populated nextPageToken means the change list can be incomplete. Google documents following continuation pages and retaining newStartPageToken for later polling after reaching the current end.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Do not acknowledge a complete sync interval before all returned continuation pages are reconciled.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does a gap in Drive notification message numbers prove a missing event

Does a gap in Drive notification message numbers prove a missing event?

Drive notification numbers increase within a channel but are not sequential. A numerical gap by itself cannot establish how many changes or notifications were lost.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Use channel scope and change-feed reconciliation rather than subtracting message numbers to count missed events.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does renewing a Drive notification channel preserve one continuous delivery identity

Does renewing a Drive notification channel preserve one continuous delivery identity?

Drive channels do not renew automatically. Replacement requires a new unique channel identifier, and the old and new channels can overlap while both remain active.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Reconcile both channel identities and expiry times; do not interpret overlapping delivery as independent source actions.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does the first Drive sync notification prove that existing files were synchronised

Does the first Drive sync notification prove that existing files were synchronised?

The sync notification signals channel startup, and can arrive before the watch response. It is not an inventory transfer or proof that the client has processed existing content.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Keep channel readiness separate from initial inventory and change-feed completion.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does a working My Drive changes integration automatically include shared drives

Does a working My Drive changes integration automatically include shared drives?

Shared-drive changes require the documented support and inclusion settings. If shared-drive support is false, shared drives and their files are excluded from the response.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Do not claim shared-drive coverage solely from successful My Drive polling.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does the Slack event authorizations field enumerate every installation that can see an event

Does the Slack event authorizations field enumerate every installation that can see an event?

Slack event envelopes provide a limited authorization view. The documented apps.event.authorizations.list method retrieves the full authorization list when that inventory is needed.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Do not infer a single visible installation from the abbreviated event envelope.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does standard Slack retry handling guarantee delivery of substantially delayed events

Does standard Slack retry handling guarantee delivery of substantially delayed events?

Slack describes Events API delivery as best effort. By default it does not attempt events more than two hours late; the optional Delayed Events setting changes late-delivery handling and adds hourly retries after the initial attempts.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Record the setting and incident interval; retries do not establish a complete historical stream.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does enabling a Slack event subscription guarantee every configured event type is delivered

Does enabling a Slack event subscription guarantee every configured event type is delivered?

Slack states that granted OAuth scopes determine which subscribed event types an installation receives. Configuring a subscription without the required granted scopes does not supply that event class.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Distinguish subscription configuration from actual grant coverage before interpreting silence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Does one Slack 429 response require stopping every workspace and API method

Does one Slack 429 response require stopping every workspace and API method?

Slack applies the documented Retry-After interval to the affected method for tokens of the app in that workspace. Other methods and the same method in other workspaces are not restricted by that specific response.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Bind retry decisions to the returned scope; do not treat the response as proof of an app-wide outage.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review

Do published Slack rate tiers apply unchanged when a client avoids cursor pagination

Do published Slack rate tiers apply unchanged when a client avoids cursor pagination?

For methods supporting cursor pagination, Slack applies the stated tier when pagination is used. Requests that avoid pagination receive stricter limits, so a tier label alone does not establish achievable inventory throughput.

Documentation reviewed 2026-10-30. Primary source.

Boundaries
  • Check the actual pagination strategy before estimating scan coverage or completion time.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

Complete record JSON · Exact free preview JSON · Source review