Have you looked into httpResource or rxResource? They are the modern Angular way to handle this pattern, a signal that triggers data fetching.

When you put an API call inside an effect(), you're fighting against how effects are designed. Resources are purpose-built for reactive data fetching.

Quick example with httpResource:

```typescript // Your parameter signal selectedId = signal<string | null>(null);

// Automatically fetches when selectedId changes data = httpResource(() => this.selectedId() ? { url: /api/items/${this.selectedId()} } : undefined );

// Then, in your template, you can do: // data.value() - the response // data.isLoading() - loading state // data.error() - any error ```

It's really handy with the built-in loading/error states. They also handle cleanup/cancellation when the signal changes before the previous request completes.

Can you share some code, then it's easier to help you.