## TL;DR

Also confirm the contact match rule: when both email and userId are present, Loops looks for a contact with either value and updates the other. Check the event pattern exists before sending the event.

## Fix

1. Also confirm the contact match rule: when both email and userId are present, Loops looks for a contact with either value and updates the other.
   Expected: You see the expected output instead of the problem.

## When to use

- You are setting up or using this Loops feature.
- The symptom matches: event sent but workflow did not fire - check the event pattern.

## When NOT to use

- Unrelated Loops issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Loops. Source: https://github.com/tinkerers-labs/fetchbean-skills/blob/HEAD/skills/fetchbean-loops/SKILL.md.

## Variant phrasings

### event sent but workflow did not fire - check the event pattern

## Why it happens

sendEvent returns success but nothing happens downstream. The event pattern the workflow listens for is the usual gap.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/tinkerers-labs/fetchbean-skills/blob/HEAD/skills/fetchbean-loops/SKILL.md