Skip to main content

Common errors

Expired invitation​

Symptom: the invitation link no longer opens the sign-up screen. How to fix: ask the person responsible for the organization to generate a new invitation.

Password reset email didn't arrive​

Symptom: you requested the reset but nothing arrived in your inbox. How to fix:

  • check the spam folder;
  • confirm the address you entered is correct;
  • if your company filters external email, ask IT to allow the RuleForge domain;
  • if your organization uses corporate SSO, your password is managed by your provider — not by RuleForge.

Version publishing is blocked​

Symptom: you click Publish and see a blocking warning. How to fix: the screen tells you which criterion failed. The most common:

  • validation errors;
  • failing regression;
  • quality score below the minimum;
  • review not yet approved.

See Versions and quality criteria to check each criterion.

Git integration test fails​

Symptom: the Test connection button returns an error. How to fix:

  • review the credential on the provider (GitHub, GitLab, or Gitea);
  • confirm it has permission to access the desired repository;
  • for GitHub, verify the GitHub App is installed on the organization that owns the repository.

Webhook test fails​

Symptom: the destination system rejects the notification. How to fix: confirm the secret configured on the webhook matches what the destination system is expecting. If you just configured it, save and test again.

I can't register a webhook URL​

Symptom: you get an invalid URL message when saving. How to fix: RuleForge only accepts public URLs (http or https). Local addresses (like localhost) or private network IPs are blocked for security.

I can't see a page​

Symptom: the menu that should appear is missing, or the action fails. How to fix: check, in this order:

  • you're in the right organization (top of the screen);
  • you have the required role — some areas only appear for administrators;
  • your organization's plan includes that feature;
  • the active project is the one you expected.

I created an API key but the value disappeared​

Symptom: after saving, the key's secret is no longer displayed. How to fix: that's expected — the value is shown only once, for security. If needed, rotate to get a new value.

SAML SSO login doesn't work as expected​

Symptom: the SAML configuration seems incomplete. How to fix: SAML is only available in preview. For production, use SSO with OIDC.

My corporate email isn't recognized for SSO​

Symptom: the login screen doesn't redirect to your company's provider. How to fix: confirm with the organization administrator that your email domain was added to the SSO provider and that the provider is active.