jasquat

Yeah that is odd. I do think the same fix would fix it. I'm not sure how this could happen without celery if it doesn't happen in non-prod. How often...

Oh, I wonder if it's related to the manual tasks after the call activities / subprocesses. Was that first screenshot taken from prod or dev.app?

@madhurrya what use are you signed in as when you see this? They may not have access to the logs api.

@madhurrya yeah it looks like internal has access to view the instances on that model. ~~Those permissions could probably be added to the "start" macro. I'm not sure if that's...

@madhurrya I think the thing to do is set the permissions properly but what should they be? Should we give the "internal" group access to read the logs for that...

So the simple way to do this is to give the desired group read access to: * `/logs/[process_model_identifier]` * `/logs/typeahead-filter-values/[process_model_identifier]` We currently do not have a permission that would allow...

@sashayar13 it seems fine to me. Any user with a status-im email address goes into the internal group so it's up to you and @harmeet-status. I think from the `/logs/*`...

The theory here is that with celery the mi child tasks are created and then saved to the db and the pi is queued to run again. This causes the...

It seems doubtful it's fixed. We think it's random. It may work sometimes and it may not others.

This will hopefully help on status envs https://github.com/status-im/infra-spiff-workflow/pull/50#pullrequestreview-2116249060 based on https://github.com/sartography/spiff-arena/issues/1498#issuecomment-2161586960.