284313f908
Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz Source: /opt/alga-psa on psa.joliet.tech
33 lines
1.0 KiB
Markdown
33 lines
1.0 KiB
Markdown
# Refresh Watch (Pub/Sub + Gmail Watch) – Admin Guide
|
||
|
||
If a Gmail provider stops receiving webhook notifications (e.g. after 7-day Gmail watch expiry or if the push endpoint URL changed) run a **Refresh Watch**. This will:
|
||
|
||
1. Re-initialise the Pub/Sub topic & subscription (bypassing the 24-hour guard).
|
||
2. Register a fresh Gmail `users.watch` subscription.
|
||
|
||
## Using the UI
|
||
|
||
Settings → Email Providers → ••• → **Refresh Watch**
|
||
|
||
The action shows a spinner and writes an audit log entry on completion.
|
||
|
||
## Using the API
|
||
|
||
```bash
|
||
curl -X POST \
|
||
-H "Authorization: Bearer <admin-token>" \
|
||
-H "Content-Type: application/json" \
|
||
-d '{"providerId":"<providerId>"}' \
|
||
https://<host>/api/email/refresh-watch
|
||
```
|
||
|
||
`200 OK` signals success.
|
||
|
||
## When to Use
|
||
|
||
* “Not receiving emails” but OAuth tokens are valid.
|
||
* Google Cloud Console shows the subscription in a **deleted** state.
|
||
* After changing the application base URL in production.
|
||
|
||
> Running the refresh multiple times in a row is safe; the operation is idempotent.
|