petergs

@eambrosyupgrade what do you mean by "2 applies"? I'm seeing similar behavior on 2.27 and can't figure this out.

OK did a little digging... In [resourceSumologicCSEMatchListCreate](https://github.com/SumoLogic/terraform-provider-sumologic/blob/b5a6461f05bedbbbc22882b95d96a510c8a7508f/sumologic/resource_sumologic_cse_match_list.go#L156C18-L156C18), existing state here for the `id` on new match list items is `known after apply`, so further on in the function when `items`...

I think the solution might be as simple as leaving `item.ID` uninitialized or set to an empty string in [resourceToCSEMatchListItem](https://github.com/SumoLogic/terraform-provider-sumologic/blob/b5a6461f05bedbbbc22882b95d96a510c8a7508f/sumologic/resource_sumologic_cse_match_list.go#L216). But I'm not sure if it's a better idea to...

Also - here's a `curl` example to reproduce the error we're seeing in debug logs. You'll need to replace the `value`s, `MATCHLIST_ID`, and `ENDPOINT` to relevant values for your environment....