Why does yc-360 say "no responsive hook found" for my Node.js process?

This message means the yc-360 script couldn't find a running yCrash Node.js hook for the process ID you gave it. The script looks for a hook that has already registered itself, and if it can't find one, there's nothing for it to connect to.

A few things to check:

• Confirm NODE_OPTIONS is actually set in the process's environment, not just in your shell session. A variable set in a terminal doesn't automatically apply to a process started from a different session, a systemd unit, or a container that was already running.
• Confirm the application was restarted after NODE_OPTIONS was set. The hook only loads when the process starts. It can't attach to an application that's already running.
• If you've set YC360_NODE_RUNTIME_DIR, confirm it's set to the exact same value on both the application and the yc-360 script. See nodejsRuntimeDir.

If none of the above resolves it, you can fall back to Signal Mode, which doesn't depend on the hook at all, though it captures a smaller set of artifacts.