My container executes successfully, but provision status is "Failed" and system logs say ContainerCrashing; why?

Question

I have an Azure Container App that continuously fails at provisioning and the logs continuously report "ContainerCrashing", however from my end I'm seeing that the container is executing and terminating successfully.

The only difference between this app and others is that this one has a cron scale rule like so:

"scale": {
    "minReplicas": 0,
    "maxReplicas": 1,
    "rules": [
      {
        "name": "cron",
        "custom": {
          "type": "cron",
          "metadata": {
            "timezone": "America/Los_Angeles",
            "start": "0-59/5 * * * *",
            "end": "1-59/5 * * * *",
            "desiredReplicas": "1"
          }
        }
      }
    ]
}

I'm guessing this is the culprit. My intent is to have an app that runs one instance to completion every five minutes. But because I can't do exactly that, I've set the rules to trigger the container to scale up from 0 to 1 instance every five minutes, then back off to 0 after 1 minute of expected run time.

It was my understanding that if I have a container that's still running after the back off period, then it'll be allowed to complete. Or if my container terminates successfully then it'll just scale itself back to 0 or restart no problem. But based on this ContainerCrashing I'm imagining the possibility that my app is somehow not behaving in a way that's compatible with the cron rules.

FYI, the troubleshooting center shows no issues with KEDA scaling and my console logs show no issues with my app.

Can anyone help me understand what might be happening?