feat: manually trigger notification #58
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add a way to manually trigger the notification clean up.
The cronjob has been added for a few days, but the notifications had not been cleaned up.
Since the strapi cloud logs are quite bad to navigate, this should give instant feedback on what's wrong.
Testing
Notification > cleanup > cleanupExpiredNotifications
:authorization: bearer <api key>
Example of a successful response:
Example of an error response: