Skip to content

Schedule status check on successful message batch request #30

Merged
steventux merged 7 commits intomainfrom
retry-batch-notification
Mar 20, 2025
Merged

Schedule status check on successful message batch request #30
steventux merged 7 commits intomainfrom
retry-batch-notification

Conversation

@steventux
Copy link
Contributor

@steventux steventux commented Mar 19, 2025

We need a way to schedule status checks from the batch processing lambda. (ignore the branch name)

We can use the boto3 client scheduler to schedule execution of a lambda.

  • Adds a scheduler class which calls the boto3 client accordingly
  • Scheduler also handles status check lambda scheduling although the implementation/integration is out of scope for this PR
  • Role and Lambda ARNs should be present in the env. TBC if this is the right approach.
  • Retries are hardwired to 5 cycles, this might be overkill, we might also want to configure per call.

We will need to schedule retries of batch notifications if the original request fails.
We also need to schedule status checks. This commit adds a class which can do both. The ARN values are TBC.
Sets a maximum retry count of 5.
@steventux steventux requested review from a team and dnimmo March 19, 2025 10:21
@steventux steventux force-pushed the retry-batch-notification branch from 28eba34 to 15bf209 Compare March 19, 2025 13:42
@steventux steventux changed the title Retry batch notifications Add scheduler Mar 19, 2025
@steventux steventux changed the title Add scheduler Add lambda scheduler Mar 19, 2025
We just want to retry 5 times at the same interval in minutes.
@steventux steventux changed the title Add lambda scheduler Schedule status check on successful message batch request Mar 19, 2025
@steventux steventux added this pull request to the merge queue Mar 20, 2025
Merged via the queue into main with commit 8f20166 Mar 20, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants