Readiness and Blockers

What this is

Readiness checks explain whether a Protege is safe to save, test, or publish.

Blockers are setup issues Hookshot™ finds before a Protege can run reliably.

Use this page when a Protege cannot be published, cannot run automatically, or shows setup warnings after a Builder plan is accepted.

The Protege needs a clear name and description.

Fix it by adding enough context that a teammate can understand what the Protege owns.

The Protege needs clear run-time rules.

Fix it by describing what the Protege should decide, what it should produce, and what it should avoid.

One or more required integrations are not connected or need repair.

Fix it by opening the integration and completing the connection or reconnection flow.

The Protege has a trigger, but the service that provides the trigger is not connected.

Fix it by connecting the source integration before expecting automatic runs.

The trigger is connected but still needs configuration, such as a project, repo, channel, team, or other provider-specific field.

Fix it by filling the required trigger input in setup or Integrations.

The trigger is registered, but Hookshot has not received the first matching event yet.

Fix it by sending a known-safe event from the connected app, then checking Event Feed.

The Protege is schedule-only but has no enabled schedule.

Fix it by adding at least one schedule with the intended cron and timezone.

Trigger Access controls what can start the Protege.

Review it when:

Tool Access controls what the Protege can do after it starts.

Review it when:

Tool Access deserves extra review for workflows that post messages, create issues, update tasks, or otherwise change another system.

You are ready to test when:

Last updated 12 days ago

Was this helpful?