Angular Ngrx Effect fails after mutiple clicks

Hello everyone,
I have built a blog app for learning angular. In this app I have a forum, with different ressorts and on this ressort page all questions to this ressort are rendered, I have on this fields a link to my singleQuestion page, where the question and its answers are rendered. This link works, I see it in the url and in the logs all functions and effects are called with the correct id of this forum question. And that works for one or two rounds where I click all the entries. But suddenly when this page opens, the url is correct, but the last opened entry is rendered and there it stucks. So I had opened the id 4, then I click on the id 5 and I have it in the url and in the logs but still the id 4 is rendered and that stays. I have broken this error down to the http-request in the effect. So this request is not made anymore after I clicked multiple questions. Here is the relevant code from my single component:

singleForum$: Observable<Forum> = this.store.select(selectForumData);
  isLoading$: Observable<boolean> = this.store.select(selectForumLoading);
  isError$: Observable<boolean> = this.store.select(selectForumError);
  message$: Observable<string>  = this.store.select(selectForumMessage);

  id = this.router.snapshot.paramMap.get('id');
  getUserId = this.singleForum$.pipe(
    map((forum)=>forum.user_id)
  )
  forumUserId = this.getUserId.subscribe()
  allAnswersToQuestion$: Observable<ForumAnswer[]> = this.store.select(selectAllAnswerToQuestion);
  isAnswerLoading$: Observable<boolean> = this.store.select(selectForumAnswerLoading);
  isAnswerError$: Observable<boolean> = this.store.select(selectForumAnswerError);
  messageAnswer$: Observable<string> = this.store.select(selectForumAnswerMessage);
  ngOnInit(): void {
      this.store.dispatch(getForum({ id: parseInt(this.id!)}));

    combineLatest([this.isError$, this.isAnswerError$]).subscribe(([isError ,isAnswerError])=>{
      if(isError){
        this.message$.subscribe((errorMessage)=>{
          this.toastr.error(errorMessage)
        })
      }
      if(isAnswerError){
        this.messageAnswer$.subscribe((errorMessage)=>{
          this.toastr.error(errorMessage)
        })
      }
    })
  }

This is the effect in my store:

getForum$ = createEffect(()=>
    this.actions$.pipe(
        ofType(getForum),
        switchMap((action)=>{
            console.log('i am triggered with', action.id)
           return this.httpClient.get(this.api_url + 'find/'+ action.id).pipe(//this is not sending after multiple clicks
                map((response:any)=>{
                    console.log(response, 'I get a response')
                    this.store.dispatch(getAllAnswersToQuestion({id: action.id}))
                    return getForumSuccess({forumData:response})
                }),
                catchError((error)=>{
                    console.log(error, 'I have one')
                    return of(getForumError({error}))
                }
            ))
        })
    )
);

I have currently no errors in console or in the devtools.
Perhaps someone have seen this behaviour before and can help.
Thanks.

Do you have a working website or is it still local? Is this an entry in the input field that stays there until the next one is entered?

Thanks for your response, this page is still local. It is no input field. This are blogentries like here on free code camp. And when we click on one of this entries another page opens, in this case the singleQuestion page, and renders the blogentry with his id an also all answers to this blogentry . So it is really similar to free code camp. You click on my entry in all javascriptQuestions and this page opens and show my detailed question and you can answer this and your answer is rendered. That works all, but when I click all questions one time for one or two rounds. This request in the effect fires not anymore. So I click the blogentry with the id 5 and I have the 5 in the url and also in my logs, so this effect is triggered with the correct id, but because this get request is not fired anymore the entry that was openend before is still rendered and that stays. So here it begins to stuck.