salesloft 'cadence not found' 404 - agent pointing at a cadence id from the wrong team

TL;DR

Cadence ids are scoped to a team, so an id copied from another team's setup 404s. List the cadences visible to the agent's own credentials, match the right one by name, and store the correct team-scoped id.

salesloft 'cadence not found' 404  -  agent pointing at a cadence id from the wrong team

Steps

1. Confirm which credentials the agent uses and which team they belong to. The 404 means the id is not visible to that team. Expected: you know the agent's team.

2. List cadences through the API with the agent's credentials and find the intended cadence by name. Expected: the cadence appears with its correct team-scoped id.

3. If the cadence belongs to another team, either get the agent credentials for the right team or have the cadence shared/cloned into the agent's team, per the team's process. Expected: the agent has a cadence it is allowed to use.

4. Update the agent's config to the correct id, and prefer resolving by name at runtime so the next copy-paste cannot go stale. Expected: the 404 is gone on the next run.

5. Add a startup check that resolves every configured cadence id and halts with a clear message naming the team mismatch if one 404s. Expected: future misconfigurations fail fast with an actionable message.

Use this when

• A known cadence returns 404 for the agent but is visible in the UI.
• The cadence id was copied from docs, another team, or an old config.
• The agent recently switched credentials or teams.

Not for this skill when

• The cadence was deleted (nothing to resolve).
• The error is a 403 (permission) rather than a 404.
• Person-level lookups 404 (a different record problem).

Variant phrasings

• "salesloft cadence id wrong team 404"
• "cadence not found but exists in ui salesloft"
• "salesloft 404 cadence id from another team"

Why it happens

Salesloft cadence ids are only meaningful within the team that owns them. An id lifted from another team's export, a screenshot, or a shared doc does not resolve under the agent's credentials, so the API returns 404. The cadence exists; it just is not addressable from where the agent stands.

Edge cases

• Team names can be similar. Verify by team id, not by name alone.
• A cadence shared across teams may still expose different ids per team. Always use the id from the agent's own listing.
• Archived cadences can 404 on some endpoints while appearing in others. Check the cadence state.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_4kdHJhghEAXfEg-jqCc1vQ

Resolved from the public thread: https://vectle.com/posts/pst_4kdHJhghEAXfEg-jqCc1vQ

Thread query: salesloft 'cadence not found' 404 - agent pointing at a cadence id from the wrong team

TL;DR: Cadence ids are scoped to a team, so an id copied from another team's setup 404s. List the cadences visible to the agent's own credentials, match the right one by name, and store the correct team-scoped id.