Improve execution/error handling for the "Subscribe to platform events" trigger

[erroneous0ne]

Description

Currently, only the first execution is relevant and contains logs, all others do nothing, it will increase logs and credentials retrieving numbers. We can only monitor errors for the flow by logs, logs will have a link to the execution which contains and will contain all future messages and errors. But since we store executions only for 30 days, and after 30 days the first execution will simply disappear we need to improve this trigger. It should work as all other triggers work, not store all messages/errors logs in one execution which becomes unavailable after some period of time. It should store each new message or error in a new execution, instead of creating a useless one.

Component Version

2.7.0

Definition of done

• [ ] Redo the saving messages/errors logs logic

[erroneous0ne]

With this improvement please add additional logs to check a connection to the Salesforce. FYI @if0s

[HannaTrotsenko]

https://github.com/elasticio/salesforce-component-v2/releases/tag/2.7.1

[erroneous0ne]

Issue solved. Slack conversation.