Skip to main content
Use this page to find the first useful check for common Custory issues.

​
Start with the symptom

Use the first check that matches what is failing now.

​
Access issues

Check these first:
  • the user joined the wrong workspace
  • the invite was sent to a different email address
  • the invitation expired
  • the invitation was already accepted or declined
  • the user is a Viewer but expects editor permissions
  • an owner has not reviewed a join request yet
Invitation acceptance is tied to the invited email address. If someone opens the link from the wrong signed-in account, ask an owner to resend the invite to the correct email.

​
Notification issues

Slack and Discord direct messages need two separate things:
  1. an active workspace-level Slack or Discord integration
  2. a personal Slack or Discord account link for the person receiving the DM
Link codes are temporary and single-use. Generate a fresh code if the current one fails.

​
Integration issues

Open Manage Integrations and check the tool’s connection state. Integrations can be:
  • active
  • expired
  • in error
If the integration is expired or in error, reconnect it before debugging the feature that depends on it. Disconnecting removes the integration from the workspace. Linked task records for that integration are also removed.

​
Automation issues

Automations can be draft, active, paused, or invalid. If an automation becomes invalid, the product stores validation errors so you can see what setup is missing. Common causes include:
  • a required integration is missing or invalid
  • the trigger is incomplete
  • the scope no longer points to valid work
  • an action is missing required fields
For failed runs, open Run history. Run results can show queued, running, succeeded, failed, or skipped states, with failed-action details where available. Only time-based automations expose Run once.

​
Metric sync issues

Metric data sources can be active, paused, or in error. If a metric does not update:
  1. open the metric item
  2. open Data source
  3. confirm the PostHog or Stripe integration is active
  4. confirm the selected source, measure, and evaluation window still make sense
  5. use Sync now
If sync fails, Custory shows a failure message and stores the source in an error state with the latest error.

​
External task issues

If a linked task looks stale:
  • confirm the integration is active
  • open the external task and confirm it still exists
  • check whether the external status changed in a way Custory can still read
  • review notifications for linked-task status changes