Skip to content
Evergrowth Documentation

An agent did not run on a record (Skipped)

A task that ends on Skipped is not an error. It means the agent looked at the record, decided there was no work to do for it, and moved on without producing a new result. That is usually deliberate: the record was set aside, already qualified, or not yet eligible for the step you asked for. This page explains how to tell which case you are in and how to make the record eligible.

Symptom

Section titled “Symptom”

In the Task feed, a task card shows the status Skipped instead of Finished. The record you expected the agent to work on has no new result from that run, and nothing went wrong - there is no red Error message and no warning.

You may also see this on an individual account or contact:

  • A DNT chip next to the record name, shown with a small minus icon.
  • An ICP Status locked marker (a small lock icon) next to the ICP status on an account.

Why this happens

Section titled “Why this happens”

A record is skipped when the agent has a clear reason not to act on it. The common reasons:

  • The record is set to Do Not Touch. Accounts and contacts carry a DNT flag. While that flag is on, agents leave the record alone so it is never re-researched, re-qualified, or contacted. This is the deliberate way to park a record, for example a current customer, a competitor, or an account you have asked agents to stay away from.

  • The account is not ICP qualified. Contact-level work depends on the account first qualifying as a fit. If the account’s ICP status is No or Inconclusive, or qualification has not run on it yet, then contact steps - finding contacts, contact qualification, research, plays, finding an email or phone - are skipped for that account. The agents only invest in contacts at accounts that fit your ideal profile.

  • The contact is not IBP qualified. Some contact-level steps - contact research and generating plays - act only on a contact that has qualified as a fit for one of your personas. If the contact’s IBP status is not Yes, or contact qualification has not run yet, those steps are skipped, and work flows to the contacts who match one of your personas. Finding an email or phone number is the exception: the Email/Phone finder runs on any contact you select, whether or not it is a persona fit, so you can still get contact details for gatekeepers or people you plan to qualify later.

  • The account belongs to a vertical with no personas. Contact qualification matches each contact against the personas defined for its account’s vertical. If that vertical has no personas defined, there is nothing to match against, so qualification is skipped for those contacts. The qualification dialog warns you about this before the run and lists the affected verticals and how many contacts each one covers.

  • The ICP status is locked. When an account’s ICP Status locked marker is on, its qualification result is frozen. Re-running qualification on a locked account will not overwrite that result - if the locked status is Yes, downstream steps proceed; if it is No or Inconclusive, qualification is skipped rather than redone. Locking is how you protect a manually confirmed decision from being changed by a later run.

  • The work was already done and reused. When you run qualification or research on a record that already has a result, the agent reuses the saved result instead of redoing it, and reports that record as skipped rather than spending credits to repeat the work. In the workflow builder, each step also carries a Use existing data from database setting: with it on, the step skips qualification and enrichment for accounts and contacts that already exist in your workspace and reuses previously saved data, processing only new or missing information.

How to fix it

Section titled “How to fix it”

Work out which reason applies, then make the record eligible:

  1. Open the record and check its chips. On the account or contact, look for a DNT chip, the ICP or IBP status, and the ICP Status locked lock icon. These tell you at a glance why the agent stood down.

  2. Take it off Do Not Touch if it should be worked. On the account or contact, open the actions menu and choose Remove from Do Not Touch. The agent will act on it the next time you run.

  3. Qualify the account first, then work its contacts. If the account’s ICP status is No, Inconclusive, or empty, run the Qualification agent on the account and let it return Yes before you run contact-level agents. See Run a Qualification agent. For the meaning of each status, see Qualification.

  4. Qualify the contact before contact research or plays. If a contact’s IBP status is not Yes, run contact qualification so it matches one of your personas before running contact research or generating plays for it. The Email/Phone finder is the exception - it runs on any selected contact without qualification. See Run a Qualification agent and Find an email or phone number.

  5. Add personas to the vertical that has none. If the warning told you a vertical has no personas, define personas for that vertical in the Agent Training Center, then re-run contact qualification. See Add personas in the Training Center.

  6. Turn off existing-data reuse in a workflow to force fresh work. If a workflow step is skipping records because it is reusing saved data, open that step in the workflow builder and turn off its Use existing data from database setting. The step will then qualify and enrich even records that already have a result. Note that this spends credits on work that was previously reused. See Build a workflow.

  7. Unlock a frozen result if it should change. If an account is skipping re-qualification because its ICP Status locked marker is on, the saved decision is being protected on purpose. Unlock it only if you intend to let agents requalify and change it.

If a task instead ended on Error, that is a different situation - see An agent task ended with an error. To watch a run move through its statuses, see Monitor the task feed.

Section titled “Related”