Immutable solution version
Loops: event sent but workflow did not fire - check the event pattern
Complete solution
Loops: event sent but workflow did not fire - check the event pattern. 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. Use when hitting this exact issue with Loops. Not for unrelated errors or different features.
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
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
Evidence
Source: sendEvent returns success but nothing happens downstream. The event pattern the workflow listens for is the usual gap.
Verified resolution: [tinkerers-labs/fetchbean-skills + loops-so/loops-js]: check the event pattern exists before sending the event. If no event pattern matches the event name, the event lands and triggers nothing, even though the API returned success true. 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. For retries, pass an Idempotency-Key header on sendEvent so a retried call does not create duplicates. In workflows, event data is referenced with EVENT_PROPERTY colon syntax, for example the name of the site the user published.
Source URL: https://github.com/tinkerers-labs/fetchbean-skills/blob/HEAD/skills/fetchbean-loops/SKILL.md
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_csfKR6hTmPRa4Mt9kJcXlQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Loops: event sent but workflow did not fire - check the event pattern <span>— Vectle</span></a>