Since this is internal Jira Cloud configuration as you cannot control who is enrolled and who is not,
I was wondering how the 409 response can be avoided.
What action triggers the rest api call for a user that is not enrolled in the context:
Is the Jira system trying to send me a message, which I cannot receive because I do not belong to a certain group ?
api endpoint:
/gateway/api/engage-targeting/api/v2/user/messages/context-group-forge-apps-changeboarding/start
Same remark for api endpoint:
gateway/api/engage-targeting/api/v2/user/messages/command-palette-issue-action-spotlight/start
[HTTP/2 409 159ms]
statusCode “409 CONFLICT”
message “User is not enrolled in message ‘command-palette-issue-action-spotlight’”
errors